GitLab

In particular do not stop the search for a suitable node, when a non-mode_is_data() node is encountered.

The verifiers for the checked nodes are at least as strict as these assert()s.

This fixes backend/spill_phi2.c.

The same check is just a few lines above.

With base the displacement may be a single byte.

The epilogue is added late, in particular after scheduling.
Therefore it is not necessary to move a mis-scheduled 'restore' directly before a 'return' anymore.

This reverts commit fa7eb6ee and
provides alternative fix for opt/boolopt4.c.

This fixes backend/subregister.c.

Except for global CSE, comparing nodes of different block always results
in 'not equal', so we should consider them for hashing beforehand.

Simply directly check the magnitude of the tarval instead of converting it to a long.
* On 64 bit hosts 32 bit operations could not match immediates with bit 31 set.
  E.g. v32 & 0xFFFFFFF0.
* On 32 bit hosts 64 bit operations with 32 bit non-negative constants were erroneously matched and caused silent miscompilation.
  E.g. v64 & 0xFFFFFFF0.
* On 32 bit hosts 64 bit operations with constants, which would fit into 32 bits, but have higher bits set, were not matched, because get_tarval_long() failed.
  E.g. v64 & 0xFFFFFFFFFFFFFFF0.