This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [libstdc++, testsuite] Add dg-require-thread-fence
- From: Mike Stump <mikestump at comcast dot net>
- To: Jonathan Wakely <jwakely at redhat dot com>
- Cc: Christophe Lyon <christophe dot lyon at linaro dot org>, "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 20 Oct 2016 09:26:19 -0700
- Subject: Re: [libstdc++, testsuite] Add dg-require-thread-fence
- Authentication-results: sourceware.org; auth=none
- References: <CAKdteObWfMso8e5R_eE=q=_ROD7nkmKphVM1=-zk_J1j+As3LA@mail.gmail.com> <20161020094008.GB2922@redhat.com> <CAKdteObZBtji1Yc+aEH0JHQRX2HcrgePrVTGUApzAmqPEiTM6A@mail.gmail.com> <20161020122040.GI2922@redhat.com>
On Oct 20, 2016, at 5:20 AM, Jonathan Wakely <jwakely@redhat.com> wrote:
>
> I am considering leaving this in the ARM backend to force people to
> think what they want to do about thread safety with statics and C++
> on bare-metal systems.
Not quite in the GNU spirit? The port people should decide the best way to get as much functionality as possible and everything should just work, no sharp edges.
Forcing people to think sounds like a sharp edge?