From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Cc: r6144 <r6k@sohu.com>, mec.gnu@mindspring.com
Subject: Re: Branch created for inter-compilation-unit references
Date: Wed, 25 Feb 2004 00:18:00 -0000 [thread overview]
Message-ID: <20040225001850.GA24036@nevyn.them.org> (raw)
In-Reply-To: <20040221200814.GA28652@nevyn.them.org>
On Sat, Feb 21, 2004 at 03:08:15PM -0500, Daniel Jacobowitz wrote:
> I've just created "drow_intercu-20040221-branch". I'm going to post and
> commit the work I've done over the past two days, which starts at the
> opposite end of the problem from several approaches I've seen here in the
> past.
> GCC HEAD can already generate the necessary debug information if you want to
> play with it; use -gdwarf-2 -feliminate-dwarf2-dups. I expect it will be at
> least a few more days before GDB can read that output.
The branch is at this point, I hope, complete. Michael, if you have
the chance, I would appreciate it if you could run it through your test
harness. I would be flabbergasted if it affected any stabs target
(there's only one trivial patch outside of dwarf2read.c), and the new
code will not be heavily exercised by current GCC output, but the risk
for the latter is higher.
If you're really feeling adventurous, you can test the new code when
using DWARF-2 and GCC 3.3-branch, 3.4-branch, HEAD, tree-ssa, et
cetera: just add "--target_board unix/-feliminate-dwarf2-dups" to
RUNTESTFLAGS. HEAD GDB will choke on this, the branch does not in my
testing.
Anyone else with a compiler that can generate this sort of data is
invited to test the branch also. Please let me know how it goes.
I will start submitting preliminary patches, those which can also act
as bug-fixes or optimizations to the current dwarf2 code, tonight or
tomorrow. Merging the branch may have to wait until after GDB 6.1.
Personally, I'd love for it to be included, since the sooner we release
a GDB that can understand this data the sooner GCC can emit it by
default; but I want at least some more testing on the branch before
I suggest that. My timing for this project was somewhat unfortunate.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-25 0:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 20:08 Daniel Jacobowitz
2004-02-25 0:18 ` Daniel Jacobowitz [this message]
2004-02-25 0:35 ` Andrew Cagney
2004-02-25 1:29 ` Daniel Jacobowitz
2004-02-25 2:23 ` Andrew Cagney
2004-02-25 2:27 ` Daniel Jacobowitz
2004-02-25 3:17 ` Andrew Cagney
2004-02-25 3:51 Michael Elizabeth Chastain
2004-02-25 5:12 ` Andrew Cagney
2004-02-25 16:10 ` Daniel Berlin
2004-02-25 17:01 ` Andrew Cagney
2004-02-25 17:07 ` Daniel Berlin
2004-02-25 18:50 ` Andrew Cagney
2004-02-25 18:53 ` Daniel Berlin
2004-02-25 19:48 ` Andrew Cagney
2004-02-26 5:48 ` Eli Zaretskii
2004-02-26 6:06 ` Daniel Berlin
2004-02-26 6:31 ` Eli Zaretskii
2004-02-26 15:05 ` Daniel Jacobowitz
2004-02-26 16:19 ` Elena Zannoni
2004-02-26 16:25 ` Daniel Jacobowitz
2004-02-26 16:36 ` Elena Zannoni
2004-02-26 16:54 ` Daniel Jacobowitz
2004-02-26 19:01 ` Eli Zaretskii
2004-02-26 19:10 ` Eli Zaretskii
2004-02-26 19:24 ` Andrew Cagney
2004-02-26 19:28 ` Daniel Jacobowitz
2004-02-26 20:19 ` Andrew Cagney
2004-02-26 5:48 ` Eli Zaretskii
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=20040225001850.GA24036@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=r6k@sohu.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