Greetings! Just a followup here. All is well with -O2. I've filed a
gcc bug describing the behavior with -O3.
Take care,
Roman Zippel <[EMAIL PROTECTED]> writes:
> Hi,
>
> Camm Maguire wrote:
>
> > Greetings! The atlas testers fail at random intervals on m68k,
>
> It would help a lot to k
Roman Zippel wrote:
> Hi,
>
> Camm Maguire wrote:
>
> >Greetings! The atlas testers fail at random intervals on m68k,
>
> It would help a lot to know on which machine it fails (esp. type of cpu).
Hi.
I think Camm was working on crest.debian.org - 060/50.
Rick
--
Hi,
Camm Maguire wrote:
Greetings! The atlas testers fail at random intervals on m68k,
It would help a lot to know on which machine it fails (esp. type of cpu).
bye, Roman
On Fri, 15 Oct 2004, Camm Maguire wrote:
> Greetings! The atlas testers fail at random intervals on m68k,
> preventing the package build to complete. I'm suspecting some cache
> or register flushing issue. When I try to stop in gdb at the point
> the corrupted value is supposedly written, the
Greetings! The atlas testers fail at random intervals on m68k,
preventing the package build to complete. I'm suspecting some cache
or register flushing issue. When I try to stop in gdb at the point
the corrupted value is supposedly written, the problem never appears.
Here are the symptoms:
===
5 matches
Mail list logo