Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: implement typed DWARF stack
Date: Thu, 05 May 2011 16:47:00 -0000	[thread overview]
Message-ID: <m3r58dxfgc.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3tydayyzq.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed,	04 May 2011 14:47:21 -0600")

>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:

Tom> I would appreciate comments on this.  In the absence of comments I am
Tom> going to check it in.

Tom> Jakub recently implemented Cary Coutant's typed DWARF stack proposal in
Tom> GCC.

I had a couple notes I wanted to make that I forgot about when I was
actually writing the email.

First, look at the dwarf2_get_die_type addition in dwarf2read.c.
I am not extremely pleased with this code.  I think due to DIE cache
flushing it may create new types from time to time.

I am not sure what to do about this.  One idea I had was that perhaps
read_type_die_1 could intern base types (meaning we would have to
re-read the DIEs but we would not instantiate new types all the time).
Another idea was to permanently cache base types by DIE -- but this
seemed like too much overhead for a reasonably obscure feature.


The other issue is that you might be wondering why I didn't update the
DWARF->AX compiler in dwarf2loc.c.  The reason is simply that this
extension is, IIUC, mostly useful for floating point and decimal
floating point, and AX cannot express those.

Maybe this can also be used for wider-than-address-sized integral types.
I will look; maybe the AX compiler does need an update for this.

Tom


  reply	other threads:[~2011-05-05 16:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 20:48 Tom Tromey
2011-05-05 16:47 ` Tom Tromey [this message]
2011-05-05 18:07 ` Ulrich Weigand
2011-05-05 18:38   ` Tom Tromey
2011-05-05 20:15     ` Tom Tromey
2011-05-09 22:02       ` Ulrich Weigand
2011-05-10 14:15         ` Tom Tromey
2011-05-11  0:15           ` Ulrich Weigand
2011-05-11 14:59             ` Tom Tromey
2011-05-11 19:44               ` Tom Tromey
2011-05-12  0:03               ` Ulrich Weigand
2011-05-12 16:33                 ` Tom Tromey
2011-05-13  7:52                   ` Regression: " Jan Kratochvil
2011-05-13 15:44                     ` Tom Tromey
2011-05-15  8:26                       ` gdbindex crash: " Jan Kratochvil
2011-05-16 17:37                         ` Tom Tromey
2011-05-17 17:01                           ` Tom Tromey
2011-05-13 17:17                     ` Tom Tromey
2011-05-13 17:34                       ` Jan Kratochvil
2011-05-12 19:32             ` Tom Tromey
2011-05-16 15:50               ` Ulrich Weigand
2011-05-16 18:09                 ` Tom Tromey
2011-05-17  8:35                   ` Jakub Jelinek
2011-06-03 13:52                     ` Tom Tromey
2011-05-10 16:39         ` Tom Tromey

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=m3r58dxfgc.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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