public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@jive.nl>
To: jimb@redhat.com
Cc: 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 09:54:00 -0000	[thread overview]
Message-ID: <200408050952.i759qXFK010181@juw15.nfra.nl> (raw)
In-Reply-To: <vt2wu0ejy1q.fsf@zenia.home> (message from Jim Blandy on 04 Aug 2004 18:14:41 -0500)

   From: Jim Blandy <jimb@redhat.com>
   Date: 04 Aug 2004 18:14:41 -0500

   > > The next step is to have something that will recognize when a series
   > > of pieces is actually a reference to a single register --- presumably
   > > one that GDB has a number for, but one that Dwarf only has numbers for
   > > pieces of.  That needs to be an arch method that recognizes the cases
   > > that can be simplified, and passes on the cases it can't handle.  This
   > > will address all the current uses of DW_OP_piece, I believe.

So we'll have to *temporary* add an arch method to several targets,
and then remove it again when we fix things properly?  I don't think
that's a good idea.

   It seems worthwhile to me, because it will allow GDB to work
   correctly, assignments and all, in the cases where the current value
   structures can handle it, and it's very little work.  At some point,
   resources will materialize to do the larger project, but what's the
   harm in getting the best behavior we can out of the current structures
   until then?

The harm is introducing hacks that are very hard to remove in the
feature.  GDB is full of such hacks, and apart from Andrew nobody
seems to actively work on trying to remove these.  We really don't
need any more of them.

Mark

  reply	other threads:[~2004-08-05  9:54 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 [this message]
2004-08-05 14:31                   ` Jim Blandy
2004-08-05 16:27                     ` Joel Brobecker
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=200408050952.i759qXFK010181@juw15.nfra.nl \
    --to=kettenis@jive.nl \
    --cc=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).