invoke.texi (fstrict-volatile-bitfields): Clarify current behavior.

2014-02-04  Bernd Edlinger  <bernd.edlinger@hotmail.de>

        * doc/invoke.texi (fstrict-volatile-bitfields): Clarify current
        behavior.

From-SVN: r207473

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 99a153bda842c2c35cf45878dc3acbd4c2144637..9647593b9b228a3d18b9220f7e52ed2e3d37718d 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2014-02-04  Bernd Edlinger  <bernd.edlinger@hotmail.de>
+
+       * doc/invoke.texi (fstrict-volatile-bitfields): Clarify current
+       behavior.
+
 2014-02-04  Richard Biener  <rguenther@suse.de>
 
        PR lto/59723

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 89e80ac130ab3fc57938bf87da7bbc96f36fc298..640c123b19c840745a2f7b4dfb246ed62d1b9b7c 100644 (file)
--- 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.