On 11/21/2013 06:23 PM, Hans-Peter Nilsson wrote:
On Thu, 21 Nov 2013, Andrew MacLeod wrote:
I can bootstrap and check this on x86 to make sure it doesnt affect anything,
and you can fool with it and see if you can get your desired results with your
port.
Success!
For the record, tested together with the attached patch for the
CRIS ports, both regularly (not finished, but done with the C
testsuite part and no regressions there), as well as manually
for the attached test-programs, compiling and inspecting output
for different sub-targets and checking that data layout,
alignment and size is as intended.
Too bad about the libstdc++ atomics, but with this/these patches
at least I'll be able to tell people that _Atomic for C11 works.
Thanks to the both of you!
All we need is a way to communicate the atomic property to the type
within the libstdc++ template... We cant use _Atomic there :-P
I originally had created an __attribute__ ((atomic)) whch you could
apply to the atomic template type and get the same behaviour as
_Atomic, Im not sure if there is another way or not. The atomic
template is generic, so I couldn't think of any special macro wizardry
we could define...
Andrew