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: Eric Botcazou <ebotcazou at adacore dot com>
- To: Jakub Jelinek <jakub at redhat 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:18:56 +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> <1846992 dot iYuoEK1jha at polaris> <20140509083543 dot GJ10386 at tucnak dot redhat dot com>
> 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 times in
> the recent history), then that results in unnecessary breakage.
IMO that's a rather weak point, if people use arbitrary snapshots then they
can revert to the previous one; similarly, if they use the SVN tree, then they
can back out the patch manually. You cannot do that for an official release.