From: Stephane Carrez <stcarrez@nerim.fr>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA/dwarf: Fix the GCC 2.95.3 store.exp regression for multi-register variables
Date: Thu, 13 Mar 2003 21:39:00 -0000 [thread overview]
Message-ID: <3E70FA76.2020105@nerim.fr> (raw)
In-Reply-To: <20030312204053.GA31861@nevyn.them.org>
Hi Daniel,
Daniel Jacobowitz wrote:
> This kills both a hack and the regression discussed on gdb@. Instead of
> returning the value of the register and the register number, if the
> expression evaluator only returns the register number, we can use
> value_from_register. This way we share multi-register variable handling
> with the non-LOC_COMPUTED case.
>
> This patch removes a FIXME and an interface I didn't much like (the lval
> argument to dwarf_expr_read_reg) so I'm pretty happy with it. Everything
> should go back to working that worked before.
>
Great!
FYI, it fixes the problem on m6811-elf (PR 1107).
Thanks,
Stephane
next prev parent reply other threads:[~2003-03-13 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 20:41 Daniel Jacobowitz
2003-03-13 21:39 ` Stephane Carrez [this message]
2003-04-03 21:52 ` Elena Zannoni
2003-04-04 6:42 Michael Elizabeth Chastain
2003-04-10 18:01 ` Elena Zannoni
2003-04-13 15:54 ` 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=3E70FA76.2020105@nerim.fr \
--to=stcarrez@nerim.fr \
--cc=drow@mvista.com \
--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