From: Tom Tromey <tromey@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Jason Merrill <jason@redhat.com>,
Richard Henderson <rth@redhat.com>,
gcc-patches@gcc.gnu.org, Steve Ellcey <sje@cup.hp.com>
Subject: Re: [PATCH] Fix up typed DWARF stack support for POINTERS_EXTEND_UNSIGNED targets (PR debug/48853)
Date: Thu, 12 May 2011 19:55:00 -0000 [thread overview]
Message-ID: <m3fwojnbsv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <BANLkTikY3OFT1KuuZSSxMVxyLusvhf+p9A@mail.gmail.com> (H. J. Lu's message of "Thu, 12 May 2011 08:36:46 -0700")
>>>>> "H.J." == H J Lu <hjl.tools@gmail.com> writes:
H.J.> On Thu, May 12, 2011 at 7:56 AM, Jakub Jelinek <jakub@redhat.com> wrote:
>> On Wed, May 11, 2011 at 12:28:18PM -0700, H.J. Lu wrote:
>>> This patch restores the old behavior for Pmode. OK for trunk if there
>>> are no regressions?
>>
>> That is IMHO wrong, ignoring subregs is a very bad idea.
>> While you can workaround generation of the DW_OP_GNU_convert that way
>> (why do you want that?, just install newer gdb that has typed dwarf stack
>> support, coming hopefully soon), you'd get incorrect debug info for
>> long long to int casts.
>>
H.J.> I will wait for the new gdb.
I'm going to commit the changes today.
Tom
prev parent reply other threads:[~2011-05-12 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 9:22 Jakub Jelinek
2011-05-05 14:53 ` Jason Merrill
2011-05-05 15:24 ` Jakub Jelinek
2011-05-05 15:29 ` Jason Merrill
2011-05-07 5:21 ` H.J. Lu
2011-05-09 19:24 ` Jason Merrill
2011-05-11 22:14 ` H.J. Lu
2011-05-12 16:40 ` Jakub Jelinek
2011-05-12 17:38 ` H.J. Lu
2011-05-12 19:55 ` Tom Tromey [this message]
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=m3fwojnbsv.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=rth@redhat.com \
--cc=sje@cup.hp.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).