[PATCH] Fix C++0x memory model for -fno-strict-volatile-bitfields on ARM
Bernd Edlinger
bernd.edlinger@hotmail.de
Mon Nov 18 11:10:00 GMT 2013
Hi,
On Fri, 15 Nov 2013 13:30:51, Richard Biener wrote:
>> That looks like always pretending it is a bit field.
>> But it is not a bit field, and bitregion_start=bitregion_end=0
>> means it is an ordinary value.
>
> I don't think it is supposed to mean that. It's supposed to mean
> "the access is unconstrained".
>
Ok, agreed, I did not regard that as a feature.
And apparently only the code path in expand_assigment
really has a problem with it.
So here my second attempt at fixing this.
Boot-strapped and regression-tested on x86_64-linux-gnu.
OK for trunk?
Thanks
Bernd.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: changelog-unaligned-data.txt
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20131118/9dfd8796/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch-unaligned-data.diff
Type: application/octet-stream
Size: 1341 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20131118/9dfd8796/attachment.obj>
More information about the Gcc-patches
mailing list