From: "H . J . Lu" <hjl@lucon.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC] GDB's mdebug support vs. GCC 3.0
Date: Fri, 29 Jun 2001 13:20:00 -0000 [thread overview]
Message-ID: <20010629132011.A26294@lucon.org> (raw)
In-Reply-To: <20010629131300.A5247@nevyn.them.org>
On Fri, Jun 29, 2001 at 01:13:00PM -0700, Daniel Jacobowitz wrote:
> On Fri, Jun 29, 2001 at 01:09:12PM -0700, H . J . Lu wrote:
> > On Fri, Jun 29, 2001 at 12:39:44PM -0700, Daniel Jacobowitz wrote:
> > > The stabs support for mips-linux is now much more complete than it was; from
> > > what I can see this is because we started using config/elfos.h in gcc. Two
> > > of the gems we get from this are EINCL/BINCL stabs, which as far as I can
> > > see we did not before, and a trailing SO at the end of a file.
> > >
> >
> > Since you mentioned mdebug and mips-linux, I assume you are aware that
> > Linux/MIPS no longer uses mdebug. I have changed it to MIPS_STABS_ELF.
>
> I'm aware of that, yes. GCC 3.0 emits mdebug, however. With 3.0.1
> hopefully we can stop using the mdebug code. Or simply switch to
> DWARF2; I'm still not clear on why we haven't done that already.
I don't think so. GCC 3.0 doesn't emit mdebug, only stabs. It is gas
who does mdebug or MIPS_STABS_ELF.
BTW, gcc 3.0 doesn't work tool well on Linux/mips. I submitted a few
patches. But .....
H.J.
next prev parent reply other threads:[~2001-06-29 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 12:39 Daniel Jacobowitz
2001-06-29 13:09 ` H . J . Lu
2001-06-29 13:13 ` Daniel Jacobowitz
2001-06-29 13:20 ` H . J . Lu [this message]
2001-07-19 14:31 ` Elena Zannoni
[not found] ` <20010719160858.A30318@nevyn.them.org>
2001-07-19 20:18 ` Elena Zannoni
2001-07-19 22:41 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010629132011.A26294@lucon.org \
--to=hjl@lucon.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox