aboutsummaryrefslogtreecommitdiff
path: root/binutils/testsuite/binutils-all/i386
diff options
context:
space:
mode:
authorJan Beulich <jbeulich@suse.com>2025-03-21 08:33:39 +0100
committerJan Beulich <jbeulich@suse.com>2025-03-21 08:33:39 +0100
commit37a1bbe9d56e0fc6093a687c55023db7d465da86 (patch)
tree9747a1c07f3f51a741d411df287453febaa7a480 /binutils/testsuite/binutils-all/i386
parentbc965121b5f02eeb52e2fc6acc94c042bb3ace02 (diff)
downloadbinutils-37a1bbe9d56e0fc6093a687c55023db7d465da86.zip
binutils-37a1bbe9d56e0fc6093a687c55023db7d465da86.tar.gz
binutils-37a1bbe9d56e0fc6093a687c55023db7d465da86.tar.bz2
aarch64: simplify RCPC3 unpredictable logic
The original observation was that STILP is warned about when everything is fine. Documentation, not just for STILP, says explicitly that behavior is identical to respective pre-existing insns (for STILP in particular that's STP). With that it's unclear why distinct logic was added: Other code can be re-used, simply distinguishing by the number of operands. This was diagnostics also end up more consistent. Along with adding some STILP uses to the (positive) testcase, also add a pair of STLR to similarly demonstrate that the register overlap goes without warning when there's no write-back.
Diffstat (limited to 'binutils/testsuite/binutils-all/i386')
0 files changed, 0 insertions, 0 deletions