diff options
| author | Ramana Radhakrishnan <ramana.radhakrishnan@arm.com> | 2017-12-05 16:32:55 +0000 |
|---|---|---|
| committer | Ramana Radhakrishnan <ramana@gcc.gnu.org> | 2017-12-05 16:32:55 +0000 |
| commit | 7109d224774bce3eb27e945b2e2f7ec9d7620fa9 (patch) | |
| tree | d9d3cd25b698db0b880e696ea059d924ce156c96 /libcpp | |
| parent | 26c2efbc5a9baa65dfcffaf40e00955076574147 (diff) | |
| download | gcc-7109d224774bce3eb27e945b2e2f7ec9d7620fa9.zip gcc-7109d224774bce3eb27e945b2e2f7ec9d7620fa9.tar.gz gcc-7109d224774bce3eb27e945b2e2f7ec9d7620fa9.tar.bz2 | |
[Patch ARM] Fix probe_stack constraint.
The probe_stack pattern uses r0 as a fixed register. This can cause issues if we have auto-increment instructions coming out that have r0 as the base register.
Tested with a bootstrap and regression run. richi reports that the original issue was fixed in the run. I did consider whether probe_stack_range was affected but it all comes back to probe_stack pattern so I think we are ok.
I don't have a testcase that seems to provoke this but it seems to be default on most distributions so I'm expecting the testcoverage to come from there.
Applied.
Ramana
PR target/82248
* config/arm/arm.md (probe_stack) : Use the 'o' constraint.
From-SVN: r255428
Diffstat (limited to 'libcpp')
0 files changed, 0 insertions, 0 deletions