Re: [m68k] PING: two unreviewed ColdFire patches

[Bernardo Innocenti <bernie at develer dot com>]

Roger Sayle wrote:
> On Thu, 24 Feb 2005, Bernardo Innocenti wrote:
>
> > I'm currently bootstrapping mainline on that m68k box.  If everything
> > goes well, I'll have a compiler ready by tomorrow and test-results
> > (without the patch) before Sunday.  Then I'll apply the patch and
> > re-run the testsuite.  Testing m68k patches is not for the impatient ;-)
> >
> > gcc/
> > 2004-12-06  Peter Barada  <peter@the-baradas.com>
> > 	* config/m68k/m68k.h (HARD_REGNO_MODE_OK): Disallow bytes
> > 	in address registers.
> > 	* config/m68k/m68k.c (hard_regno_mode_ok): Likewise.
> > 	* config/m68k/m68k.md: Replace 's' with 'i' in 4th
> > 	alternative of addsi3_5200.
>
>
> This revised patch is OK for mainline, once bootstrap and regression
> testing completes.  With a four or five day turn-around for a baseline
> and the patch itself should be around next Thursday or Friday :)
>
> Thanks for your patience,

After trying to get meaningful test results for several
days, I've only got partial success.

Many tests fail because they hit the 300 seconds timeout.
The test system I've been kindly given access to is also
being used to build Debian, so it's quite busy.

I couldn't figure out an easy way to increase the timeout
without hacking dejagnu's system installation, which I
can't do from my user account.  Building the uberbaum
tree is not an option as it would take a few more days :-)

Moreover, I've even also lost the original testresult
files by mistake (working over ssh with a 2 seconds lag
is error prone), so I can't compare the results.

I've skimmed through the gcc.log and g++.log.  Besides the
timeouts, there are a few ICEs here and there.  None of
them appears to be related to my patch, but I can't be sure.

I'd like to test again on the 4.0 branch, but not
until I find out how to increase the timeout.

--
 // Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/  http://www.develer.com/