CDImode in reg

[Aurelien Buhrig]

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
>