This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: testsuite question
- From: Richard Guenther <richard dot guenther at gmail dot com>
- To: Christian Grössler <chris at groessler dot org>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 22 Feb 2011 11:05:27 +0100
- Subject: Re: testsuite question
- References: <4D62D891.5070207@groessler.org>
On Mon, Feb 21, 2011 at 10:26 PM, Christian Grössler
<chris@groessler.org> wrote:
> On 19.02.11 23:01, Richard Guenther wrote:
>>
>> On Sat, Feb 19, 2011 at 10:53 PM, Christian Grössler
>> <chris@groessler.org> ?wrote:
>>>
>>> The failures come from the assembler which complains about the out of
>>> range
>>> shift counts.
>>>
>>> Should I disable them or is there any reason unknown to me that these
>>> tests
>>> make sense?
>>
>> You need to make sure that the tests only invoke undefined behavior
>> at runtime, thus emit valid assembly from your target description.
>
> Thanks. So I can simply mask the shift count to be in the supported range,
> or even generate a nops for the instructions, correct?
Yes. Other targets simply truncate the shift count (which is usually
what CPUs do when the shift count is a register).
Richard.
> chris
>