aboutsummaryrefslogtreecommitdiff
path: root/libjava/java/security
diff options
context:
space:
mode:
authorAndrew Pinski <andrew.pinski@oss.qualcomm.com>2025-11-07 14:01:33 -0800
committerAndrew Pinski <andrew.pinski@oss.qualcomm.com>2025-11-07 18:11:30 -0800
commit77e10b47f25d05d51a187822fe6a8366a6d68d67 (patch)
tree08d87a0bdcc5ea31d6ab5667f3f5326136f81fd1 /libjava/java/security
parentcbded1ce012d6444d4ff8adbad047cf04220fe1b (diff)
downloadgcc-77e10b47f25d05d51a187822fe6a8366a6d68d67.zip
gcc-77e10b47f25d05d51a187822fe6a8366a6d68d67.tar.gz
gcc-77e10b47f25d05d51a187822fe6a8366a6d68d67.tar.bz2
sccp: Fix order of removal of phi (again) [PR122599]
This time we are gimplifying the expression and call fold_stmt during the gimplification (which is fine) but since we removed the phi and the expression references ssa names in the phi indirectly, things just fall over inside the ranger. This moves the removal of the phi until gimplification happens as it might refer back to the ssa name that the phi defines. Pushed as obvious after bootstrap test on x86_64-linux-gnu. PR tree-optimization/122599 gcc/ChangeLog: * tree-scalar-evolution.cc (final_value_replacement_loop): Move the removal of the phi until after the gimplification of the final value expression. gcc/testsuite/ChangeLog: * gcc.dg/torture/pr122599-1.c: New test. Signed-off-by: Andrew Pinski <andrew.pinski@oss.qualcomm.com>
Diffstat (limited to 'libjava/java/security')
0 files changed, 0 insertions, 0 deletions