diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2022-07-30 07:39:48 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-30 07:39:48 +0900 |
| commit | 36ab4ec2dc1795ed1d700d80437963c049ed551a (patch) | |
| tree | 26a4fc099dbb82c8209d148cd12ad4916204f031 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 3924dac7bb29bc8eb348059c901e8f912399c857 (diff) | |
| parent | 2eac6f30c8a1cd59dc640bf68bc58eb7fe656d61 (diff) | |
| download | rust-36ab4ec2dc1795ed1d700d80437963c049ed551a.tar.gz rust-36ab4ec2dc1795ed1d700d80437963c049ed551a.zip | |
Rollup merge of #99227 - Lokathor:fix-thumbv4t-none-eabi-frame-pointer, r=davidtwco
Fix thumbv4t-none-eabi frame pointer setting The `thumb_base` profile has changed since I last remember seeing it, and now it sets the frame pointer to "always keep", which is not desired for this target. Hooking a debugger to the running program is not really done, it's preferable to have the register available for actual program use, so the default "may omit" is now set. I thought that the target was already using "may omit" when I checked on it last month, because I forgot that the target was previously based on `thumb_base` rather than `Default::default()`. I only noticed the issue just now when creating the `armv4t-none-eabi` target (https://github.com/rust-lang/rust/pull/99226), though this PR is not in any way conditional on that one.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions