This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: IA32 bootstrap error
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: rth at redhat dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 30 Dec 01 18:03:51 EST
- Subject: Re: IA32 bootstrap error
> If so, how do you expect people to do work on GCC on IA32?
Use cvs gdb. And cvs binutils.
It's all one product, you see. If the parts of the toolchain
are not tested together then it's virtually certain that they
won't work together.
It's one thing for it to be required that they *work together*, but a
vastly different one that the latest version of each is required for
GCC. We always used to require that GCC work with an older version of
each of these tools and I think that's still critical.
Each of these have different release schedules and there are different
constraints on each of them. For example, somebody may be using a GDB
that was heavily modified to work on a particular embedded system:
it's not reasonable to require them to get those modifications working
on the latest GDB in order to benefit from the latest GCC. Likewise
for binutils if some peculiar object format needs to be supported.
I think the SC needs to address this issue. Not everbody is doing
development on workstations and not everybody who is on workstations
is in a position to constantly get the "latest and greatest" of
everything.