register renaming causes many ARM testsuite failures
Bernd Schmidt
bernds@redhat.com
Tue Jan 2 09:24:00 GMT 2001
On Sat, 30 Dec 2000, Philip Blundell wrote:
> Many test cases are failing to compile at -O3 using the trunk sources on ARM
> targets, with errors like this:
>
> /tmp/cc4c42x1.s: Assembler messages:
> /tmp/cc4c42x1.s:21: Error: Bad range in register list
> /tmp/cc4c42x1.s:23: Error: Bad range in register list
> /tmp/cc4c42x1.s:24: Error: Bad range in register list
> /tmp/cc4c42x1.s:25: Error: Bad range in register list
> /tmp/cc4c42x1.s:28: Error: Bad range in register list
> /tmp/cc4c42x1.s:31: Error: Bad range in register list
> /tmp/cc4c42x1.s:57: Error: Bad range in register list
> /tmp/cc4c42x1.s:59: Error: Bad range in register list
> /tmp/cc4c42x1.s:60: Error: Bad range in register list
> /tmp/cc4c42x1.s:61: Error: Bad range in register list
>
> The problem is that an insn like this matches the special `load multiple'
> pattern which generates an LDM instruction:
Apparently the constraints on the ldmsi patterns aren't strict enough.
Bernd
More information about the Gcc-bugs
mailing list