From: Andreas Schwab <schwab@suse.de>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
gcc-patches@gcc.gnu.org, Richard Biener <rguenther@suse.de>,
Bernd Schmidt <bschmidt@redhat.com>,
law@redhat.com
Subject: Re: Do not use TYPE_CANONICAL in useless_type_conversion
Date: Fri, 16 Oct 2015 15:08:00 -0000 [thread overview]
Message-ID: <87r3kuvot1.fsf@igel.home> (raw)
In-Reply-To: <20151016064309.GD45365@kam.mff.cuni.cz> (Jan Hubicka's message of "Fri, 16 Oct 2015 08:43:09 +0200")
Jan Hubicka <hubicka@ucw.cz> writes:
>> Jan Hubicka <hubicka@ucw.cz> writes:
>>
>> > Does the patch in https://gcc.gnu.org/ml/gcc-patches/2015-10/msg00902.html help?
>>
>> No, it doesn't.
>>
> Andreas,
> I am sorry for getting late to this. I hoped that the alternative patch by Alexandre would fix this.
> I still don't know how to reproduce without IA-64 box, so I am attaching a patch that I think should
> fix it. Does the attached patch work?
With that patch I'm getting a different ICE:
| in expand_debug_locations, at cfgexpand.c:5265 |
| Error detected around ../../gcc/ada/par_sco.adb:2690:10 |
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2015-10-16 15:03 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 22:11 Jan Hubicka
2015-10-01 8:33 ` Richard Biener
2015-10-01 17:51 ` Jan Hubicka
2015-10-02 7:45 ` Richard Biener
2015-10-02 6:43 ` Jan Hubicka
2015-10-02 7:56 ` Richard Biener
2015-10-02 16:02 ` Jan Hubicka
2015-10-02 18:00 ` Jan Hubicka
2015-10-02 21:16 ` Eric Botcazou
2015-10-02 21:41 ` Jan Hubicka
2015-10-02 21:52 ` Jan Hubicka
2015-10-05 12:54 ` Bernd Schmidt
2015-10-05 15:35 ` Jan Hubicka
2015-10-06 11:18 ` Richard Biener
2015-10-06 17:54 ` Jan Hubicka
2015-10-07 6:00 ` Jan Hubicka
2015-10-07 8:52 ` Richard Biener
2015-10-08 3:49 ` Jan Hubicka
2015-10-08 7:48 ` Richard Biener
2015-10-08 16:20 ` Jan Hubicka
2015-10-08 10:51 ` Richard Biener
2015-10-08 20:30 ` Jan Hubicka
2015-10-08 23:24 ` Jan Hubicka
2015-10-09 8:19 ` Richard Biener
2015-10-09 8:29 ` Eric Botcazou
2015-10-09 7:36 ` Eric Botcazou
2015-10-09 17:55 ` Jan Hubicka
2015-10-13 8:09 ` Alexandre Oliva
2015-10-13 8:39 ` Richard Biener
2015-10-13 9:20 ` Eric Botcazou
2015-10-13 16:36 ` Alexandre Oliva
2015-10-14 4:34 ` Jan Hubicka
2015-10-14 20:15 ` Alexandre Oliva
2015-10-08 10:54 ` Eric Botcazou
2015-10-08 16:03 ` Jan Hubicka
2015-10-08 16:10 ` Andreas Schwab
2015-10-08 23:05 ` Jan Hubicka
2015-10-09 9:18 ` Andreas Schwab
2015-10-09 18:34 ` Jan Hubicka
2015-10-16 6:45 ` Jan Hubicka
2015-10-16 15:08 ` Andreas Schwab [this message]
2015-10-01 14:11 ` Eric Botcazou
2015-10-01 14:28 ` Richard Biener
2015-10-01 14:39 ` Eric Botcazou
2015-10-01 17:44 ` Jan Hubicka
2015-10-02 7:43 ` Eric Botcazou
2015-10-02 8:00 ` Richard Biener
2015-10-02 8:37 ` Eric Botcazou
2015-10-02 7:39 ` Richard Biener
2015-10-02 7:48 ` Eric Botcazou
2015-10-02 8:03 ` Richard Biener
2015-10-02 11:30 Bernd Edlinger
2015-10-02 21:31 ` Eric Botcazou
2015-10-03 16:23 ` Bernd Edlinger
2015-10-03 21:31 ` Eric Botcazou
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=87r3kuvot1.fsf@igel.home \
--to=schwab@suse.de \
--cc=bschmidt@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@redhat.com \
--cc=rguenther@suse.de \
/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).