This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[RFC][PING^2] Do not consider volatile asms as optimization barriers #1
- From: Yury Gribov <y dot gribov at samsung dot com>
- To: Jakub Jelinek <jakub at redhat dot com>, Eric Botcazou <ebotcazou at adacore dot com>, gcc-patches at gcc dot gnu dot org, Hans-Peter Nilsson <hp at bitrange dot com>, rdsandiford at googlemail dot com
- Date: Thu, 17 Apr 2014 16:08:14 +0400
- Subject: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1
- Authentication-results: sourceware.org; auth=none
- References: <2417129 dot VoWsWu5CJz at polaris> <alpine dot BSF dot 2 dot 02 dot 1403110135580 dot 78203 at arjuna dot pair dot com> <87txb4wh98 dot fsf at talisman dot default> <3263590 dot RRmfNF86xv at polaris> <87a9cuin6x dot fsf at talisman dot default> <20140313072630 dot GQ22862 at tucnak dot redhat dot com> <53313702 dot 4070709 at samsung dot com>
----------------------------------------------
From: Yury Gribov <y.gribov@samsung.com>
Sent: Tuesday, March 25, 2014 11:57AM
To: Jakub Jelinek <jakub@redhat.com>, Eric Botcazou
<ebotcazou@adacore.com>, gcc-patches@gcc.gnu.org, Hans-Peter Nilsson
<hp@bitrange.com>, rdsandiford@googlemail.com
Subject: Re: [RFC] Do not consider volatile asms as optimization barriers #1
On 03/25/2014 11:57 AM, Yury Gribov wrote:
Jakub Jelinek wrote:
Richard Sandiford wrote:
OK, how about this? It looks like the builtins.c and stmt.c stuff
wasn't
merged until 4.9, and at this stage it seemed safer to just add the same
use/clobber sequence to both places.
Please wait a little bit, the patch has been committed to the trunk only
very recently, we want to see if it has any fallout.
It has been two weeks since Richard commited this to trunk. Perhaps it's
ok to backport to 4.8 branch now?
-Y
Link to original email:
http://gcc.gnu.org/ml/gcc-patches/2014-03/msg01306.html