On 01/10/14 14:44, Eric Botcazou wrote:
In my backend movdi pattern has unfortunately code '0' (depends on pattern declaration order). When gcc tried to determine if my DI regs can be saved and restore as 'caller saves' (in caller-save.c::init_caller_save()) it failed on this wrong assertion.I'd arrange for avoiding code 0 instead because this disables the cache.
Agreed, but the assert in caller-save is still wrong and ought to be fixed. jeff
