aboutsummaryrefslogtreecommitdiff
path: root/gcc/fortran/trans-expr.cc
diff options
context:
space:
mode:
authorAlexandre Oliva <oliva@adacore.com>2024-12-20 18:02:08 -0300
committerAlexandre Oliva <oliva@gnu.org>2025-01-06 18:59:00 -0300
commit1b1a33f76879dae3e6c2c1e8fb3656b0adb52ad5 (patch)
tree47d129e84c85418fb1e750924e566ca2d96ba4ca /gcc/fortran/trans-expr.cc
parent6069f02a486054484ad638b083cb3b9486bb4321 (diff)
downloadgcc-1b1a33f76879dae3e6c2c1e8fb3656b0adb52ad5.zip
gcc-1b1a33f76879dae3e6c2c1e8fb3656b0adb52ad5.tar.gz
gcc-1b1a33f76879dae3e6c2c1e8fb3656b0adb52ad5.tar.bz2
expand: drop stack adjustments after barrier [PR118006]
A gimple block with __builtin_unreachable () can't have code after it, and gimple optimizers ensure there isn't any, even without optimization. But if the block requires stack adjustments, e.g. because of a call that passes arguments on the stack, expand will emit that after the barrier, and then rtl checkers rightfully complain. Arrange to discard adjustments after a barrier. Strub expanders seem to be necessary to bring about the exact conditions that require stack adjustments after the block that ends with a __builtin_unreachable call. for gcc/ChangeLog PR middle-end/118006 * cfgexpand.cc (expand_gimple_basic_block): Do not emit pending stack adjustments after a barrier. for gcc/testsuite/ChangeLog PR middle-end/118006 * gcc.target/i386/strub-pr118006.c: New.
Diffstat (limited to 'gcc/fortran/trans-expr.cc')
0 files changed, 0 insertions, 0 deletions