diff options
| author | Jeff Law <jlaw@ventanamicro.com> | 2023-10-16 17:14:38 -0600 |
|---|---|---|
| committer | Jeff Law <jlaw@ventanamicro.com> | 2023-10-16 17:16:12 -0600 |
| commit | b626751a4e87b090531c648631df33ac20c4fab8 (patch) | |
| tree | 7afd40c2c81c97f46b08ed1e830cf6409d1591f3 /gcc/cp/ChangeLog | |
| parent | 04013e4464020b4440aa41524a222658d7e36937 (diff) | |
| download | gcc-b626751a4e87b090531c648631df33ac20c4fab8.zip gcc-b626751a4e87b090531c648631df33ac20c4fab8.tar.gz gcc-b626751a4e87b090531c648631df33ac20c4fab8.tar.bz2 | |
Fix minor problem in stack probing
probe_stack_range has an assert to capture the possibility that that
expand_binop might not construct its result in the provided target.
We triggered that internally a little while ago. I'm pretty sure it was in the
testsuite, so no new testcase. The fix is easy, copy the result into the
proper target when needed.
Bootstrapped and regression tested on x86.
gcc/
* explow.cc (probe_stack_range): Handle case when expand_binop
does not construct its result in the expected location.
Diffstat (limited to 'gcc/cp/ChangeLog')
0 files changed, 0 insertions, 0 deletions