This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: IA32 bootstrap error
- From: Daniel Berlin <dan at cgsoftware dot com>
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Sun, 30 Dec 2001 18:53:26 -0500 (EST)
- Subject: Re: IA32 bootstrap error
On Sun, 30 Dec 2001, Richard Kenner wrote:
> > 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.
Okay, well, then you are introducing a co-dependency here, requiring gcc
not to emit things gdb's non-standards compliant dwarf2 reader can't
support in the non-cvs version.
This is a bad idea.
GCC is following the standard here, it's gdb that is at fault.
If you want some option to let you use an even less dwarf2 2.0 compliant
version of gdb, it should, at most, be a configure option.
>
> 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"?
Errr, this was the answer to people for many moons for 3.0 (5.1 can barely
support
it too, but it can at least demangle things, IIRC).
--Dan