| commit | 227887ae724776730f55198d702d539bcfafe9c5 | |
| author | ktkachov <ktkachov@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Fri, 19 Jan 2018 10:26:53 +0000 (19 10:26 +0000) | ||
| committer | ktkachov <ktkachov@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Fri, 19 Jan 2018 10:26:53 +0000 (19 10:26 +0000) | ||
| tree | f072c8205ad37492e55630b8efe5769aabb096ad | treesnapshot (tar.gz zip) |
| parent | 1a9bd16aaa7ba3dfd6713376f3c1ae0245c512fc | commitdiff |
[arm] Fix gcc.target/arm/pr40956.c
The scan-assembler tests here check for MOVS for Thumb1 and MOV for Thumb2,
but in fact there's no reason why we wouldn't generate MOVS for Thumb2 as well,
it really depends on a lot of optimisation decisions.
The only behaviour we want to test is that we move a 0 constant into a register
only once, which can be achieved with either MOV or MOVS.
Simplify the check by always checking for either MOV or MOVS.
* gcc.target/arm/pr40956.c: Adjust scan-assembler pattern.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@256880 138bc75d-0d04-0410-961f-82ee72b054a4
The scan-assembler tests here check for MOVS for Thumb1 and MOV for Thumb2,
but in fact there's no reason why we wouldn't generate MOVS for Thumb2 as well,
it really depends on a lot of optimisation decisions.
The only behaviour we want to test is that we move a 0 constant into a register
only once, which can be achieved with either MOV or MOVS.
Simplify the check by always checking for either MOV or MOVS.
* gcc.target/arm/pr40956.c: Adjust scan-assembler pattern.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@256880 138bc75d-0d04-0410-961f-82ee72b054a4
| gcc/testsuite/ChangeLog | diffblobblamehistory | |
| gcc/testsuite/gcc.target/arm/pr40956.c | diffblobblamehistory |