This is the mail archive of the 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]

Re: powerpc-ibm-aix4.3.3.0 bootstrap issue


Alexandre Oliva wrote:
> On Oct  5, 2001, David Edelsohn <> wrote:
> >       Using a debugger on the compiler producing different output caused
> > the compiler to stop emitting different output.
> Gee!  I suppose the cat is neither dead nor alive, then :-)
> If you run the compiler outside the debugger, does it reliably produce
> different output?  Given that timing doesn't play a role in GCC, I
> really don't see how a debugger could affect the output of the
> program, assuming you're not issuing commands to modify the state of
> the inferior program, such as setting variables, issuing calls, etc.
> This makes me wonder whether there's some kernel problem that fails to
> preserve the upper 32 bits of 64-bit registers in certain corner cases
> on context switches, or something like that.  This would explain the
> irreproducibility of the failures, and the reason why it was when
> HOST_WIDE_INT became `long long' that it started showing up.
> Does this make any sense to you?
> --
> Alexandre Oliva   Enjoy Guarana', see
> Red Hat GCC Developer                  aoliva@{,}
> CS PhD student at IC-Unicamp        oliva@{,}
> Free Software Evangelist    *Please* write to mailing lists, not to me

I thought this had been sorted out?

Wasn't this fixed by this patch

Wed Oct 10 00:41:29 EDT 2001  John Wehle  (

        * rs6000.c (rs6000_emit_load_toc_table): Don't
        strdup the toc label.
        (create_TOC_reference): Likewise.


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