> From: Andrew MacLeod <amacl...@redhat.com> > Date: Mon, 7 Nov 2011 05:25:15 +0100
> On 11/06/2011 07:38 PM, Hans-Peter Nilsson wrote: > > > > This (formally a change in the range 181027:181034) got me three > > libstdc++ regressions for cris-elf, which has no "atomic" > > support whatsoever (well, not the version represented in > > "cris-elf"), so something is amiss at the bottom of the default > > path: > yes, I have a final pending patch which didn't make it to the branch > before the merge. It changes the behaviour of atomic_flag on targets > with no compare_and_swap. I *think* it will resolve your problem. > > I've attached the early version of the patch which you can try. Its > missing a documentation change I was going to add tomorrow before > submitting, but we can see if it resolves your problem. Give it a shot > and let me know. Sorry, no it didn't help. No additional regressions either though, but the undef'd reference changed to two: Excess errors: /tmp/atreg1/gccobj/cris-elf/libstdc++-v3/include/bits/atomic_base.h:273: undefined reference to `std::atomic_thread_fence(std::memory_order)' /tmp/atreg1/gccobj/cris-elf/libstdc++-v3/include/bits/atomic_base.h:274: undefined reference to `__sync_lock_test_and_set_1' collect2: error: ld returned 1 exit status brgds, H-P
