diff options
| author | Eric Botcazou <ebotcazou@adacore.com> | 2022-10-29 10:16:18 +0200 |
|---|---|---|
| committer | Eric Botcazou <ebotcazou@adacore.com> | 2022-10-29 14:10:45 +0200 |
| commit | 96ba0c369ee86d61b6df2f8fb8364028a113acf7 (patch) | |
| tree | 40918ab8225545cac6614d7e2368ad399f8654e8 /libbacktrace | |
| parent | 7e7ebe3e350fde90fe49ab41ce3b92a811bb6370 (diff) | |
| download | gcc-96ba0c369ee86d61b6df2f8fb8364028a113acf7.zip gcc-96ba0c369ee86d61b6df2f8fb8364028a113acf7.tar.gz gcc-96ba0c369ee86d61b6df2f8fb8364028a113acf7.tar.bz2 | |
Restore RTL alias analysis for hard frame pointer
The change:
2021-07-28 Bin Cheng <bin.cheng@linux.alibaba.com>
alias.c (init_alias_analysis): Don't skip prologue/epilogue.
broke the alias analysis for the hard frame pointer (when it is used as a
frame pointer, i.e. when the frame pointer is not eliminated) described in
the large comment at the top of the file, because static_reg_base_value is
set for it and, consequently, new_reg_base_value too.
When the instruction saving the stack pointer into the hard frame pointer in
the prologue is processed, it is viewed as a second set of the hard frame
pointer and to a different value by record_set, which then proceeds to reset
new_reg_base_value to 0 and the game is over.
gcc/
* alias.cc (init_alias_analysis): Do not record sets to the hard
frame pointer if the frame pointer has not been eliminated.
Diffstat (limited to 'libbacktrace')
0 files changed, 0 insertions, 0 deletions