From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Enhance stabs reader to better deal with forward references
Date: Tue, 27 Mar 2007 16:29:00 -0000 [thread overview]
Message-ID: <20070327162947.GC3452@caradoc.them.org> (raw)
In-Reply-To: <20070228201201.GH13140@adacore.com>
On Wed, Feb 28, 2007 at 12:12:01PM -0800, Joel Brobecker wrote:
> 2007-02-08 Joel Brobecker <brobecker@adacore.com>
>
> * stabsread.c (add_undefined_type): Add extra parameter.
> Now handles nameless types separately.
> (struct nat): New type.
> (noname_undefs, noname_undefs_allocated, noname_undefs_length):
> New static variables.
> (read_type): Update calls to add_undefined_type.
> (add_undefined_type_noname): New function.
> (add_undefined_type_1): Renames from add_undefined_type.
> (cleanup_undefined_types_noname): New function.
> (cleanup_undefined_types_1): Renames cleanup_undefined_types.
> (cleanup_undefined_types): New handles nameless types separately.
> (_initialize_stabsread): Initialize our new static constants.
>
> The following patch has been tested on x86-linux with -gstabs+.
> OK to apply?
This is OK.
> +/* Make a list of nameless type that are undefined.
"types"
> + In practice, we actually maintain two such list: The first list
"lists"
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-27 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 19:40 Joel Brobecker
2007-02-27 16:50 ` Daniel Jacobowitz
2007-02-28 5:48 ` Joel Brobecker
2007-02-28 11:42 ` Daniel Jacobowitz
2007-02-28 20:12 ` Joel Brobecker
2007-03-27 16:29 ` Daniel Jacobowitz [this message]
2007-03-29 18:35 ` Joel Brobecker
2007-03-31 20:42 ` Pedro Alves
2007-04-02 6:59 ` Joel Brobecker
2007-04-02 8:51 ` Pierre Muller
2007-04-02 11:05 ` Daniel Jacobowitz
2007-04-03 0:13 ` Pedro Alves
2007-04-03 3:50 ` Christopher Faylor
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=20070327162947.GC3452@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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