From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org,
Joel Brobecker <brobecker@adacore.com>,
Jim Blandy <jimb@red-bean.com>, Tobias Burnus <burnus@net-b.de>
Subject: Re: [patch] [VLA 2/2] Interpret FIELD_LOC_KIND_DWARF_BLOCK fields
Date: Tue, 20 Jan 2009 03:57:00 -0000 [thread overview]
Message-ID: <20090120035737.GA12571@caradoc.them.org> (raw)
In-Reply-To: <200901191521.n0JFLAtI004277@d12av02.megacenter.de.ibm.com>
On Mon, Jan 19, 2009 at 04:21:10PM +0100, Ulrich Weigand wrote:
> Making this dwarf2-specific function directly callable seems to break
> the abstraction layer that "hides" specific details of any particular
> debug info formati from common code.
>
> However, I'm not sure I see a clean solution for this. Ideally, we'd
> have something like a LOC_COMPUTED with callback functions, to handle
> format-specific field_loc_kind values. But that would require adding
> a new pointer to "struct field", which I don't really like either as
> this is a quite space-critical data structure ...
What fields use this - is it specific to array bounds? If so can we
move it to a new array-specific extension to struct type?
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-01-20 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 1:42 Jan Kratochvil
2009-01-19 15:22 ` Ulrich Weigand
2009-01-20 3:57 ` Daniel Jacobowitz [this message]
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=20090120035737.GA12571@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=burnus@net-b.de \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=jimb@red-bean.com \
--cc=uweigand@de.ibm.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