From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: Fix PR debug/66728
Date: Fri, 21 Aug 2015 16:20:00 -0000 [thread overview]
Message-ID: <55D74E35.7010005@redhat.com> (raw)
In-Reply-To: <87io88920k.fsf@e105548-lin.cambridge.arm.com>
On 08/21/2015 07:58 AM, Richard Sandiford wrote:
> This is yet another bug caused by rtx having modeless scalar integer
> constants. We need to use context to find the actual mode of a
> CONST_INT or CONST_WIDE_INT.
We've been bumping into these as long as I can remember. I suspect I
still have a great essay from Jim on why it's hard to fix on a hard
drive from one of my old HP boxes from the early 90s ;-)
> gcc/
> PR debug/66728
> * dwarf2out.c (loc_descriptor): Remove redundant GET_MODE of
> CONST_WIDE_INTs. Handle BLKmode for CONST_WIDE_INT too.
> (add_const_value_attribute): Add a mode parameter.
> Check it for CONST_INT and CONST_WIDE_INT. Use it to build
> wide_int values.
> (add_location_or_const_value_attribute): Update call.
> (tree_add_const_value_attribute): Likewise.
I'll have to defer to Jason & Jakub on this. Note Jakub is on PTO right
now.
jeff
next prev parent reply other threads:[~2015-08-21 16:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 14:24 Richard Sandiford
2015-08-21 16:20 ` Jeff Law [this message]
2015-10-28 12:04 ` [ping] " Ulrich Weigand
2015-10-28 13:14 ` Richard Sandiford
2015-10-28 14:25 ` Bernd Schmidt
2015-10-28 14:58 ` Ulrich Weigand
2015-11-02 15:30 ` Richard Sandiford
2015-11-02 16:29 ` Richard Sandiford
2015-11-02 20:34 ` [ping] " Mike Stump
2015-11-02 20:55 ` Richard Sandiford
2015-11-02 23:29 ` Mike Stump
2015-11-03 8:46 ` Richard Sandiford
2015-11-03 21:59 ` Mike Stump
2015-11-04 9:43 ` Richard Biener
2015-11-04 11:58 ` Mike Stump
2015-11-04 12:15 ` Richard Biener
2015-11-04 19:36 ` Mike Stump
2015-11-04 20:51 ` Richard Sandiford
2015-11-04 23:45 ` Mike Stump
2015-11-05 12:32 ` Richard Biener
2015-11-06 1:35 ` Mike Stump
2015-11-06 13:06 ` Richard Biener
2015-11-09 18:47 ` Mike Stump
2015-08-22 8:04 Uros Bizjak
2015-08-22 8:47 ` Uros Bizjak
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=55D74E35.7010005@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).