From: Joel Brobecker <brobecker@gnat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Mark Kettenis <kettenis@jive.nl>,
drow@false.org, cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: interface to partial support for DW_OP_piece in dwarf2expr.[ch]
Date: Thu, 05 Aug 2004 16:27:00 -0000 [thread overview]
Message-ID: <20040805162734.GG1192@gnat.com> (raw)
In-Reply-To: <vt2llgtd5h6.fsf@zenia.home>
> Again, I don't see any need for GDB to be broken until the larger
> project is complete. GDB is broken for targets today that could use
> this reduction method.
I must say I am pretty convinced by Jim's argument. Once we have a fully
functional op_piece mechanism in place, removing the temporary hack
should have no effect at all. I would have been hesitant to go that
route too, except that Jim said it's not much work at all.
--
Joel
next prev parent reply other threads:[~2004-08-05 16:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 7:15 Jim Blandy
2004-08-04 16:53 ` Andrew Cagney
[not found] ` <vt2fz7292z3 dot fsf at zenia dot home>
[not found] ` <41112BAE dot 9080304 at gnu dot org>
[not found] ` <vt2hdri4mi1 dot fsf at zenia dot home>
[not found] ` <41115B4F dot 1080700 at gnu dot org>
[not found] ` <vt2pt66zgul dot fsf at zenia dot home>
2004-08-04 18:26 ` Jim Blandy
2004-08-04 18:32 ` Andrew Cagney
2004-08-04 21:35 ` Jim Blandy
2004-08-04 21:55 ` Andrew Cagney
2004-08-04 22:22 ` Jim Blandy
2004-08-04 23:04 ` Daniel Jacobowitz
2004-08-04 23:17 ` Jim Blandy
2004-08-05 9:54 ` Mark Kettenis
2004-08-05 14:31 ` Jim Blandy
2004-08-05 16:27 ` Joel Brobecker [this message]
2004-08-05 18:45 ` Jim Blandy
2004-08-05 18:47 ` Daniel Jacobowitz
2004-08-05 19:56 ` Andrew Cagney
2004-08-05 20:36 ` Daniel Jacobowitz
2004-08-05 20:50 ` Andrew Cagney
2004-08-06 9:39 ` Eli Zaretskii
2004-08-10 19:55 ` Jim Blandy
2004-08-11 20:31 ` Jim Blandy
2004-08-11 20:33 ` 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=20040805162734.GG1192@gnat.com \
--to=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=kettenis@jive.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).