From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [3/3] RFC - optional patch to restore DW_AT_data_member_location
Date: Wed, 12 Sep 2012 14:36:00 -0000 [thread overview]
Message-ID: <87k3vz71h2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87r4q771xr.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed, 12 Sep 2012 08:25:52 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> I'll at least add some comments to the .S.
Tom> I suppose this is another way that having a DWARF assembler would be
Tom> preferable.
I recreated the .S and edited in some #ifs so you can see what the
changes are.
Tom
next prev parent reply other threads:[~2012-09-12 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 18:22 Tom Tromey
2012-08-21 22:12 ` Doug Evans
2012-08-24 16:53 ` Jan Kratochvil
2012-09-02 15:04 ` Joel Brobecker
2012-09-11 20:42 ` Tom Tromey
2012-08-26 8:12 ` Jan Kratochvil
2012-09-11 20:56 ` Tom Tromey
2012-09-12 13:25 ` Jan Kratochvil
2012-09-12 14:26 ` Tom Tromey
2012-09-12 14:36 ` Tom Tromey [this message]
2012-09-12 14:39 ` Tom Tromey
2012-09-26 19:11 ` 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=87k3vz71h2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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