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: dan at cgsoftware dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 30 Dec 01 18:41:25 EST
- Subject: Re: IA32 bootstrap error
> Do you really mean to require using an unreleased GDB in order to debug
> programs produced by GCC?
Yes, in order to debug an unreleased version of gcc.
What's the problem?
For one thing, it means that people who want to test the new version
of GCC will also have to test that new version of GDB, which may not
be something they want to do.
For another, using the cvs head of a package can require knowlege of
that package's internals to fix any bugs you run into. GCC knowlege
is quite specialized, as is GDB knowlege. The number of people who
know both is *very* small and the number who know both *well* is
probably very close to zero.
It is expected that gdb will release a version that supports the
features once gcc is released (IE soon after).
And what if they don't? Is the GCC release schedule to be held hostage
to the GDB release schedule or are we going to tell people "oh, by the way,
if you you want to debug programs produced by GCC 3.1, you'll have to
pick up this untested GDB"?