Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1

2014-05-13 Thread Eric Botcazou
The point of it is that the release branches are actually used by GCC users, many people don't use just official releases, but arbitrary snapshots from the release branches. If a potentially risky patch is applied immediately also to release branches and soon needs follow-ups (happened many

Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1

2014-05-13 Thread Eric Botcazou
OK, thanks. Richard also gave an RM's OK on IRC so I've now applied it. Thanks! -- Eric Botcazou

Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1

2014-05-13 Thread Jakub Jelinek
On Tue, May 13, 2014 at 07:18:56PM +0200, Eric Botcazou wrote: The point of it is that the release branches are actually used by GCC users, many people don't use just official releases, but arbitrary snapshots from the release branches. If a potentially risky patch is applied immediately

Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1

2014-05-13 Thread Eric Botcazou
Even with official release you can apply a patch, that is not the point. The point is that many people expect the release branches (and IMHO rightly so) to be supposedly stable all the time, rather than being seriously unstable most of the time and only converging to stability around the

Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1

2014-05-13 Thread Jakub Jelinek
On Tue, May 13, 2014 at 07:34:51PM +0200, Eric Botcazou wrote: Even with official release you can apply a patch, that is not the point. The point is that many people expect the release branches (and IMHO rightly so) to be supposedly stable all the time, rather than being seriously unstable

Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1

2014-05-09 Thread Eric Botcazou
It has been two weeks since Richard commited this to trunk. Perhaps it's ok to backport to 4.8 branch now? Richard, can you do that before the 4.8.3 release? Thanks in advance. -- Eric Botcazou

Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1

2014-05-09 Thread Richard Sandiford
Eric Botcazou ebotca...@adacore.com writes: It has been two weeks since Richard commited this to trunk. Perhaps it's ok to backport to 4.8 branch now? Richard, can you do that before the 4.8.3 release? Thanks in advance. Sure, that'd be fine by me. I'm not sure whether the backport has been

Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1

2014-05-09 Thread Jakub Jelinek
On Fri, May 09, 2014 at 10:16:14AM +0200, Eric Botcazou wrote: Sure, that'd be fine by me. I'm not sure whether the backport has been approved yet though. At least it looks fine to me... [I still don't grasp this wait-a-little-before-backporting policy, it always leads to forgotten

Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1

2014-05-09 Thread Richard Sandiford
Eric Botcazou ebotca...@adacore.com writes: Sure, that'd be fine by me. I'm not sure whether the backport has been approved yet though. At least it looks fine to me... OK, thanks. Richard also gave an RM's OK on IRC so I've now applied it. [I still don't grasp this