From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: Fix PR debug/66728
Date: Sat, 22 Aug 2015 08:47:00 -0000 [thread overview]
Message-ID: <CAFULd4bnFWA1mg-=1A_BPSc_J-JPwHCZwH8_=kYv+wukj6bDSA@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4YvCqTj_cvDbgCbqHkb_oeaShBwS4-_7gCEkshJdn7Png@mail.gmail.com>
On Sat, Aug 22, 2015 at 10:02 AM, Uros Bizjak <ubizjak@gmail.com> wrote:
> Hello!
>
>> 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.
>
> +++ b/gcc/testsuite/gcc.dg/debug/dwarf2/pr66728.c
> @@ -0,0 +1,14 @@
> +/* { dg-do compile { target { x86_64-*-* && lp64 } } } */
>
> Please also add i*86-*-* target with x86_64-*-*. These two should go
> together, even when additional lp64 selector is used.
Actually, i?86-*-*
Uros.
next prev parent reply other threads:[~2015-08-22 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 8:04 Uros Bizjak
2015-08-22 8:47 ` Uros Bizjak [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-21 14:24 Richard Sandiford
2015-08-21 16:20 ` Jeff Law
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='CAFULd4bnFWA1mg-=1A_BPSc_J-JPwHCZwH8_=kYv+wukj6bDSA@mail.gmail.com' \
--to=ubizjak@gmail.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).