[Bug libstdc++/70560] Review configure checks for _GLIBCXX_ATOMIC_BUILTINS and atomicity_dir

2021-04-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70560 Jonathan Wakely changed: What|Removed |Added Assignee|redi at gcc dot gnu.org|unassigned at gcc dot gnu.org

[Bug libstdc++/70560] Review configure checks for _GLIBCXX_ATOMIC_BUILTINS and atomicity_dir

2020-08-17 Thread james.hilliard1 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70560 --- Comment #7 from James Hilliard --- (In reply to Jonathan Wakely from comment #6) > (In reply to James Hilliard from comment #5) > > That might be somewhere here: > > http://autobuild.buildroot.org/results/3be/ > >

[Bug libstdc++/70560] Review configure checks for _GLIBCXX_ATOMIC_BUILTINS and atomicity_dir

2020-08-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70560 --- Comment #6 from Jonathan Wakely --- (In reply to James Hilliard from comment #5) > That might be somewhere here: > http://autobuild.buildroot.org/results/3be/ > 3bedf404de0ea42ee3ba624cded65d310a847af9/apcupsd-3.14.14/config.log No, I meant

[Bug libstdc++/70560] Review configure checks for _GLIBCXX_ATOMIC_BUILTINS and atomicity_dir

2020-08-17 Thread james.hilliard1 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70560 --- Comment #5 from James Hilliard --- (In reply to Jonathan Wakely from comment #4) > (In reply to James Hilliard from comment #2) > > We've been hitting a bug in buildroot with an application(apcupsd) that > > links against libsupc++.a

[Bug libstdc++/70560] Review configure checks for _GLIBCXX_ATOMIC_BUILTINS and atomicity_dir

2020-08-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70560 --- Comment #4 from Jonathan Wakely --- (In reply to James Hilliard from comment #2) > We've been hitting a bug in buildroot with an application(apcupsd) that > links against libsupc++.a directly. Maybe I missed it, but I don't see the linker

[Bug libstdc++/70560] Review configure checks for _GLIBCXX_ATOMIC_BUILTINS and atomicity_dir

2020-08-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70560 --- Comment #3 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #1) > It would be better to fix the lock policy at configure-time, so it is a > constant for a given build of libstdc++. That was done for PR 67843 with r266533,

[Bug libstdc++/70560] Review configure checks for _GLIBCXX_ATOMIC_BUILTINS and atomicity_dir

2020-08-17 Thread james.hilliard1 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70560 James Hilliard changed: What|Removed |Added CC||james.hilliard1 at gmail dot com ---

[Bug libstdc++/70560] Review configure checks for _GLIBCXX_ATOMIC_BUILTINS and atomicity_dir

2017-06-23 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70560 --- Comment #1 from Jonathan Wakely --- A related issue is that we decide on shared_ptr locking policy based on a dynamic property that can change between translation units according to -march: static const _Lock_policy __default_lock_policy

[Bug libstdc++/70560] Review configure checks for _GLIBCXX_ATOMIC_BUILTINS and atomicity_dir

2016-11-19 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70560 Andrew Pinski changed: What|Removed |Added Target Milestone|7.0 |---

[Bug libstdc++/70560] Review configure checks for _GLIBCXX_ATOMIC_BUILTINS and atomicity_dir

2016-04-06 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70560 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|