This is the mail archive of the
mailing list for the GCC project.
Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Eric Botcazou <ebotcazou at adacore dot com>
- Cc: gcc-patches at gcc dot gnu dot org, Richard Sandiford <rdsandiford at googlemail dot com>, Yury Gribov <y dot gribov at samsung dot com>, Hans-Peter Nilsson <hp at bitrange dot com>
- Date: Tue, 13 May 2014 19:47:02 +0200
- Subject: Re: [RFC][PING^2] Do not consider volatile asms as optimization barriers #1
- Authentication-results: sourceware.org; auth=none
- References: <2417129 dot VoWsWu5CJz at polaris> <2996385 dot 0IegOxgcxB at polaris> <20140513172531 dot GY10386 at tucnak dot redhat dot com> <5095847 dot OHKfMgBTgS at polaris>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
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 most of the time and only converging to stability around the
> > official releases.
> Possibly, but with our scheme it's the opposite: it's stable most of the time
> and series of patches are applied just before the releases...
That's not completely true. Some people do (at least for the non-risky
changes) backports immediately, others often do it in batches, days to weeks
to months after trunk commits, but most of the batches aren't close to releases.
If you look e.g. at 4.8 branch, there were less than 50 (non-DATESTAMP)
commits in the last month, but more than 300 (non-DATESTAMP) commits this year
(and quite a few in between 4.8.2 release and New Year). So I'd say the
last month on 4.8 branch was pretty much a normal month on the branch,