This is the mail archive of the
mailing list for the GCC project.
Re: powerpc-ibm-aix220.127.116.11 bootstrap issue
- To: rth at redhat dot com
- Subject: Re: powerpc-ibm-aix18.104.22.168 bootstrap issue
- From: mike stump <mrs at windriver dot com>
- Date: Wed, 24 Oct 2001 15:41:21 -0700 (PDT)
- Cc: aoliva at redhat dot com, dje at watson dot ibm dot com, gcc at gcc dot gnu dot org, grahams at redhat dot com, john at feith dot com
> Date: Wed, 24 Oct 2001 14:48:05 -0700
> From: Richard Henderson <firstname.lastname@example.org>
> To: mike stump <email@example.com>
> On Wed, Oct 24, 2001 at 02:42:59PM -0700, mike stump wrote:
> > > From: Alexandre Oliva <firstname.lastname@example.org>
> > > Date: 24 Oct 2001 17:48:35 -0200
> > > But I still don't see how this would lead to bootstrap compare
> > > failures, or to differences not showing up when the compiler is run
> > > inside a debugger.
> > For much the same reason that:
> > might print Hi, or Hello.
> No. The important part is >>when .. run inside a debugger<<.
No, the important part is bootstrap failure... That was the part I
was mainly answering.
> The important part is >>when .. run inside a debugger<<.
bootstrap failures are in some ways, more important that differing
results in gdb.
> Nothing should change when run inside a debugger except timing, and
> gcc is not timing sensitive.
I agree, in a perfect world, this is the case. However, if gcc ever
has a bug (and sometimes, it does), say, something like:
$ cat t5.c
qsort (a, 2, sizeof(char*), strcmp);
$ gdb a.out
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.5.1"...
Starting program: /tmp/a.out
then the behavior _can_ be dependent on such things. We _can_ agree
that nothing in gcc should be sensitive to these things. I was
answering the question of what to watch out for and _how_ it could
possibly be the case, _given_ that it happens.