On 19.02.11 23:01, Richard Guenther wrote:
On Sat, Feb 19, 2011 at 10:53 PM, Christian Grössler
<ch...@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?
chris
