This is the mail archive of the gcc@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: regression hunt status, question about reports to mailing list


On Thu, Dec 26, 2002 at 04:48:31PM -0500, Kaveh R. Ghazi wrote:
>  > From: Janis Johnson <janis187 at us dot ibm dot com> 
>  > 
>  > There are dozens more regressions to track down, including several for
>  > platforms that I can't test, particularly sparc.
>  > Janis
> 
> Hi Janis,
> 
> I was wondering if you could utilize your hunting method with a cross
> compiler.  If a given regression was e.g. an ICE and reproducable when
> targetting the appropriate platform, if you were supplied with the .i
> file and appropriate flags, then I'm thinking it should be possible.
> 
> If so, would you be able to track down the critical patch point for
> some of the sparc regressions I've filed?
> 
> I.e. PRs 7227, 7794, 7796, perhaps more filed elsewhere by others.  I
> can supply the specific info and .i file if the PRs aren't enough.
> 
> I think this would be a tremendously valuable addition to your already
> helpful hunting.

I was rather hoping that by providing information about how to do the
hunts, as well as the framework script, other people would join in.
I'm planning to go through my scripts that update cvs, do partial
builds, and run tests to provide some representative examples of those,
although they're all pretty straightforward.

If no one else jumps in, though, I could try some searches with cross
compilers; there's no reason that shouldn't work.  I'm on vacation
until January 2, occasionally running simple hunts while I'm doing
vacation-type things at home.

I'm running into several regressions whose searches turn up nonsensical
patches.  These are apparently bugs that show up randomly, rather than
genuine regressions.  Some of them get different results depending on
whether I run them in the foreground or from a script.  I'll look into
those and report their behavior in GNATS.  It's possible that some of
the patches I've already reported also fall into that category.

Janis


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