This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] config.gcc: Obsolete c4x.


On Tue, 3 May 2005, Ralf Corsepius wrote:

> I really don't know what broke the c4x, but I know that GCC's regression
> processing policy is ignoring problems on "non-primary target" ("It's
> not a regression, because it's not a primary target, therefore you are
> closed out from fixing anything on during most stages of development").

It's a regression, but not a release-critical one.  You can fix 
regressions on any target or language (not just primary and secondary 
targets) at any point until the release branch is frozen; indeed for minor 
targets you have *more* freedom, not less, to do potentially risky patches 
to the back-end files to fix what might not strictly be regressions, 
simply because if you break that back end not many users will be affected.  
In contrast people changing the i386 back end at a late point in the 
release cycle to fix a regression need to be much more careful about any 
other problems their changes might cause.

-- 
Joseph S. Myers               http://www.srcf.ucam.org/~jsm28/gcc/
    jsm@polyomino.org.uk (personal mail)
    joseph@codesourcery.com (CodeSourcery mail)
    jsm28@gcc.gnu.org (Bugzilla assignments and CCs)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]