This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Do not consider volatile asms as optimization barriers #1
- From: Richard Sandiford <rdsandiford at googlemail dot com>
- To: Hans-Peter Nilsson <hp at bitrange dot com>
- Cc: Eric Botcazou <ebotcazou at adacore dot com>, gcc-patches at gcc dot gnu dot org, Yury Gribov <y dot gribov at samsung dot com>
- Date: Tue, 11 Mar 2014 21:35:31 +0000
- Subject: Re: [RFC] Do not consider volatile asms as optimization barriers #1
- Authentication-results: sourceware.org; auth=none
- References: <2417129 dot VoWsWu5CJz at polaris> <87bnxnc56j dot fsf at talisman dot default> <alpine dot BSF dot 2 dot 02 dot 1403110135580 dot 78203 at arjuna dot pair dot com>
Hans-Peter Nilsson <hp@bitrange.com> writes:
> On Mon, 3 Mar 2014, Richard Sandiford wrote:
>> AIUI:
>
> Reading back the references don't yield any dissenting
> flash-backs, FWIW.
>
> So, a (use fp) then a (clobber fp)? That was probably just too
> weird for me to think of, much like a hypercorrect ending of the
> previous clause. :)
>
> Thanks for dealing with this, and for not making my initial
> nightmarish interpretation of $SUBJECT come true: "Do not
> consider volatile asms as anything we have to consider".
> At least I hope so. Dig up this horse in 6 months?
Thanks, and to Bernd for the review. I went ahead and applied it to trunk.
Richard