From: Daniel Jacobowitz <drow@false.org>
To: Andreas Jaeger <aj@suse.de>
Cc: fnf@ninemoons.com, Andrew Cagney <cagney@gnu.org>,
fnf@redhat.com, gdb@sources.redhat.com
Subject: Re: DW_OP_piece coming in gcc 3.4
Date: Tue, 17 Feb 2004 15:11:00 -0000 [thread overview]
Message-ID: <20040217151056.GA27944@nevyn.them.org> (raw)
In-Reply-To: <hosmha17fe.fsf@reger.suse.de>
On Tue, Feb 17, 2004 at 08:39:17AM +0100, Andreas Jaeger wrote:
> Fred Fish <fnf@ninemoons.com> writes:
>
> > On Monday 16 February 2004 12:25, Andrew Cagney wrote:
> >> > I've been tasked with fixing this problem, or at least deciding if it
> >> > can be fixed in the amount of time I have available to work on it.
> >>
> >> Fred, did you get anywhere with this?
> >
> > Only to the extent of determining that it was going to take more time
> > that I had immediately available to fix it in the general case, but
> > that Keith's patch could be adapted to fix the immediate problem and
> > then I could revisit this issue after some more urgent work was done.
> > I would expect that to be sometime in the next few weeks.
>
> Which patch by Keith? Can you mail the URL? I couldn't find it
> myself...
I'm guessing Fred meant Kevin's patch:
Date: Thu, 22 May 2003 10:00:39 -0700
From: Kevin Buettner <kevinb@redhat.com>
Subject: [RFA] Limited DW_OP_piece support
I asked him to do it in dwarf2_evaluate_loc_desc instead, but neither
of us had time to revisit the issue.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-17 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 16:30 Fred Fish
2004-02-06 16:36 ` Daniel Jacobowitz
2004-02-16 19:25 ` Andrew Cagney
2004-02-16 19:42 ` Fred Fish
2004-02-17 7:39 ` Andreas Jaeger
2004-02-17 15:11 ` Daniel Jacobowitz [this message]
2004-02-18 6:42 ` Fred Fish
-- strict thread matches above, loose matches on Subject: below --
2004-01-30 5:27 Michael Elizabeth Chastain
2004-01-30 5:52 ` Kevin Buettner
2004-01-30 15:06 ` 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=20040217151056.GA27944@nevyn.them.org \
--to=drow@false.org \
--cc=aj@suse.de \
--cc=cagney@gnu.org \
--cc=fnf@ninemoons.com \
--cc=fnf@redhat.com \
--cc=gdb@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