From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb@sources.redhat.com
Subject: Re: RFC: Variables in blocks of registers
Date: Sat, 01 Feb 2003 20:45:00 -0000 [thread overview]
Message-ID: <3E3C3200.8070803@redhat.com> (raw)
In-Reply-To: <20030201171001.GB29662@nevyn.them.org>
>> dwarf2 makes it possible to scatter a value across both memory and
>> registers. It's been proposed that the `struct value' be augmented with
>> something like `struct location' that knows how to find any sub
>> component of a value.
>
>
> However, right now GCC doesn't generate this. Probably because it
> would kill us.
I'm not so sure. In the past, GCC hasn't waited for GDB so I don't
think that would be the reason now.
> If I have any mental energy left after location lists,
> I may implement support for DW_OP_piece.
Perhaphs leave that one for someone else?
> Michael, I think the new multi-arch function is a good idea as long as
> it is a fallback from explicit debug info support, when we have such.
> I also think it needs a better name; but I'm not quite sure what. Hmm,
> that could be mitigated by adequate commenting.
I think it is very dangerous. It's assuming a specific algorithm in the
compiler. That locks both GDB and GCC into something of a death spiral.
I think its far better to try and get a proper location mechanism working.
Andrew
next prev parent reply other threads:[~2003-02-01 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 14:48 Mark Kettenis
2003-02-01 15:48 ` Andrew Cagney
2003-02-01 17:09 ` Daniel Jacobowitz
2003-02-01 20:45 ` Andrew Cagney [this message]
2003-02-02 16:13 ` Mark Kettenis
2003-02-02 5:21 ` Daniel Jacobowitz
2003-02-02 16:52 ` Andrew Cagney
2003-02-02 16:27 ` Daniel Jacobowitz
2003-02-04 2:31 ` Jim Blandy
2003-02-04 4:07 ` Daniel Berlin
2003-02-02 15:33 ` Daniel Berlin
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=3E3C3200.8070803@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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