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
This commit is contained in:
parent
f34ffd403d
commit
229e56f91e
@ -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
|
||||
|
@ -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.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user