| commit | 53fd0f5b1fd737a208c12909fa1188281cb370a3 | |
| author | John David Anglin <danglin@gcc.gnu.org> | |
| Thu, 14 Mar 2024 18:32:56 +0000 (14 18:32 +0000) | ||
| committer | John David Anglin <danglin@gcc.gnu.org> | |
| Thu, 14 Mar 2024 18:32:56 +0000 (14 18:32 +0000) | ||
| tree | 302ec5470b41a2065c9fffba5b08e052ef3890a2 | treesnapshot (tar.gz zip) |
| parent | 6cf4286ff9456685a29812a3560d00b956d62c39 | commitdiff |
hppa: Fix REG+D address support before reload
When generating PA 1.x code or code for GNU ld, floating-point
accesses only support 5-bit displacements but integer accesses
support 14-bit displacements. I mistakenly assumed reload
could fix an invalid 14-bit displacement in a floating-point
access but this is not the case.
2024-03-14 John David Anglin <danglin@gcc.gnu.org>
gcc/ChangeLog:
PR target/114288
* config/pa/pa.cc (pa_legitimate_address_p): Don't allow
14-bit displacements before reload for modes that may use
a floating-point load or store.
When generating PA 1.x code or code for GNU ld, floating-point
accesses only support 5-bit displacements but integer accesses
support 14-bit displacements. I mistakenly assumed reload
could fix an invalid 14-bit displacement in a floating-point
access but this is not the case.
2024-03-14 John David Anglin <danglin@gcc.gnu.org>
gcc/ChangeLog:
PR target/114288
* config/pa/pa.cc (pa_legitimate_address_p): Don't allow
14-bit displacements before reload for modes that may use
a floating-point load or store.
| gcc/config/pa/pa.cc | diffblobblamehistory |