From: Christophe Lyon <christophe.lyon@linaro.org>
To: Mike Stump <mikestump@comcast.net>
Cc: Jonathan Wakely <jwakely@redhat.com>,
Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [libstdc++, testsuite] Add dg-require-thread-fence
Date: Mon, 14 Nov 2016 19:58:00 -0000 [thread overview]
Message-ID: <CAKdteOacymxhSZVAwe8axFWr8nzrTHnc5d+pDOy=H9x=Vh23NA@mail.gmail.com> (raw)
In-Reply-To: <341FEC7E-6E51-4EFC-AD91-D4B708DC7011@comcast.net>
On 14 November 2016 at 18:54, Mike Stump <mikestump@comcast.net> wrote:
> On Oct 21, 2016, at 1:00 AM, Christophe Lyon <christophe.lyon@linaro.org> wrote:
>>
>> So if we say that the current behaviour has to keep being the default,
>> so that users think about what they are really doing,
>
> Having a toolchain not work by default to force users to think, isn't a winning strategy.
>
> Everything should always, just work. Those things that don't, we should fix.
>
I tend to agree :-)
Maybe Ramana changed his mind and would now no longer want to force
users to think?
next prev parent reply other threads:[~2016-11-14 19:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 7:55 Christophe Lyon
2016-10-20 9:19 ` Christophe Lyon
2016-10-20 9:40 ` Jonathan Wakely
2016-10-20 9:51 ` Jonathan Wakely
2016-10-20 12:01 ` Christophe Lyon
2016-10-20 12:20 ` Jonathan Wakely
2016-10-20 16:26 ` Mike Stump
2016-10-20 16:34 ` Jonathan Wakely
2016-10-20 16:51 ` Ville Voutilainen
2016-10-20 17:34 ` Mike Stump
2016-10-20 17:41 ` Jonathan Wakely
2016-11-14 13:32 ` Christophe Lyon
2016-11-15 11:50 ` Jonathan Wakely
2016-11-16 21:19 ` Christophe Lyon
2016-11-28 21:41 ` Christophe Lyon
2016-11-29 20:19 ` Jonathan Wakely
2016-11-30 8:51 ` Christophe Lyon
2016-11-30 11:23 ` Jonathan Wakely
2016-10-21 8:00 ` Christophe Lyon
2016-10-21 11:14 ` Kyrill Tkachov
2016-11-14 17:54 ` Mike Stump
2016-11-14 19:58 ` Christophe Lyon [this message]
[not found] ` <CAJA7tRbeR-z-NZgk72odwPM=iUzQq5G18i8qMgvQ9hX7QOZL+w@mail.gmail.com>
2016-11-14 20:49 ` Mike Stump
2016-11-15 8:32 ` Christophe Lyon
2016-10-20 16:51 ` Jonathan Wakely
2016-10-20 16:58 ` Ville Voutilainen
2016-10-20 17:08 ` Mike Stump
2016-10-20 17:11 ` Ville Voutilainen
2016-10-21 7:53 ` Christophe Lyon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKdteOacymxhSZVAwe8axFWr8nzrTHnc5d+pDOy=H9x=Vh23NA@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=ramana.radhakrishnan@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).