From: Ian Lance Taylor <iant@google.com>
To: Aurelien Buhrig <aurelien.buhrig.gcc@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: CDImode in reg
Date: Tue, 04 Oct 2011 16:19:00 -0000 [thread overview]
Message-ID: <mcr4nzopw5v.fsf@coign.corp.google.com> (raw)
In-Reply-To: <CAJ-J9_WRCzXe7uTS13+FB=OOg7VCr_qA5CqPjYWqQkvpgT2JRg@mail.gmail.com> (Aurelien Buhrig's message of "Tue, 4 Oct 2011 16:52:57 +0200")
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.
Ian
> 2011/10/4 Ian Lance Taylor <iant@google.com>:
>> Aurelien Buhrig <aurelien.buhrig.gcc@gmail.com> writes:
>>
>>> I'm trying to get the gcc testsuite passing for my new target port.
>>> The last ICE deals with complex long long (gcc.c-torture/compile/20000804-1.c).
>>
>> As you can see from the test file, several targets skip this test using
>> dg-skip-if.
>>
>> Ian
>>
next prev parent reply other threads:[~2011-10-04 16:19 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 [this message]
2011-10-04 17:00 ` Aurelien Buhrig
2011-10-04 18:22 ` Ian Lance Taylor
2011-10-05 7:31 ` Aurelien Buhrig
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=mcr4nzopw5v.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=aurelien.buhrig.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).