From 229e56f91e19b4b7015139a6cbe5fc77cec2ebe1 Mon Sep 17 00:00:00 2001 From: Bernd Edlinger Date: Tue, 4 Feb 2014 15:18:34 +0000 Subject: [PATCH] invoke.texi (fstrict-volatile-bitfields): Clarify current behavior. 2014-02-04 Bernd Edlinger * doc/invoke.texi (fstrict-volatile-bitfields): Clarify current behavior. From-SVN: r207473 --- gcc/ChangeLog | 5 +++++ gcc/doc/invoke.texi | 4 ++++ 2 files changed, 9 insertions(+) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 99a153bda84..9647593b9b2 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2014-02-04 Bernd Edlinger + + * doc/invoke.texi (fstrict-volatile-bitfields): Clarify current + behavior. + 2014-02-04 Richard Biener PR lto/59723 diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 89e80ac130a..640c123b19c 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -22463,6 +22463,10 @@ read or write that is correctly aligned for the target machine. In this case GCC falls back to generating multiple accesses rather than code that will fault or truncate the result at run time. +Note: Due to restrictions of the C/C++11 memory model, write accesses are +not allowed to touch non bit-field members. It is therefore recommended +to define all bits of the field's type as bit-field members. + The default value of this option is determined by the application binary interface for the target processor.