From: Aurelien Buhrig <aurelien.buhrig.gcc@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: CDImode in reg
Date: Wed, 05 Oct 2011 07:31:00 -0000 [thread overview]
Message-ID: <CAJ-J9_Xpjk3CQot8j_y7jw58pwh92XP_yghAxMDk8ckSdqASSg@mail.gmail.com> (raw)
In-Reply-To: <mcrsjn8obvl.fsf@coign.corp.google.com>
The ICE is caused by a gcc_assert(have_regs_of_mode[CDImode])) in
init_move_cost(CDImode)...
Aurélien
2011/10/4 Ian Lance Taylor <iant@google.com>:
> Aurelien Buhrig <aurelien.buhrig.gcc@gmail.com> writes:
>
>>>> So it should be skipped and the ICE is the normal behavior for such
>>>> irrelevant test cases ?
>>>
>>> Personally, I don't really think an ICE is ever an acceptable result
>>> from the compiler. However, there are practical considerations. Nobody
>>> is ever going to write code like that for your processor. If gets an
>>> ICE, no real programmer is ever going to notice. And if it didn't get
>>> an ICE it would get an error instead. So it's really up to you how much
>>> effort you want to put in to generating a proper error message rather
>>> than an ICE.
>>
>> I agree. BTW, I wonder how I could handle such an ICE from my backend
>> if I wanted to.
>
> I don't know--I don't know exactly what is causing the ICE.
>
> Ian
>
next prev parent reply other threads:[~2011-10-05 7:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 9:33 Aurelien Buhrig
2011-10-04 14:07 ` Ian Lance Taylor
2011-10-04 14:53 ` Aurelien Buhrig
2011-10-04 15:52 ` Segher Boessenkool
2011-10-04 16:19 ` Ian Lance Taylor
2011-10-04 17:00 ` Aurelien Buhrig
2011-10-04 18:22 ` Ian Lance Taylor
2011-10-05 7:31 ` Aurelien Buhrig [this message]
2011-10-05 13:55 ` Ian Lance Taylor
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=CAJ-J9_Xpjk3CQot8j_y7jw58pwh92XP_yghAxMDk8ckSdqASSg@mail.gmail.com \
--to=aurelien.buhrig.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).