https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116643
Bug ID: 116643
Summary: PHI_RESULT vs gimple_phi_result/gimple_phi_result_ptr
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: internal-improvement
Severity: enhancement
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
I noticed (even in the same file/function), that sometimes
PHI_RESULT/PHI_RESULT_PTR is used while sometimes
gimple_phi_result/gimple_phi_result_ptr is used.
We should decide on one or another and remove the other. We should also maybe
use references and remvore gimple_phi_result_ptr even.
I am filing this as I am looking into tree-ssa-phiopt.cc which uses both and
depends on where the code was partialy copied from and if it was originally
before gimple tuples. There is no decent pattern on which one gets used when
either and by who. The same person could add a new use of either even.
