https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122273
--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <[email protected]>: https://gcc.gnu.org/g:0a999da1c8842fd94706c13ced15a5205f497ecf commit r16-4446-g0a999da1c8842fd94706c13ced15a5205f497ecf Author: Andrew Pinski <[email protected]> Date: Tue Oct 14 10:36:03 2025 -0700 debug_tree: print out clique/base for MEM_REF/TARGET_MEM_REF While debugging PR 122273, I noticed that print_node was not printing out the clique/base for MEM_REF/TARGET_MEM_REF. This made harder to understand why operand_equal_p (without looking into the code) would be rejecting two looking the same MEM_REFs. Changes since v1: * v2: Don't print out clique/base if clique is 0. Bootstrapped and tested on x86_64-linux-gnu. gcc/ChangeLog: * print-tree.cc (print_node): Print out clique/base for MEM_REF and TARGET_MEM_REF. Signed-off-by: Andrew Pinski <[email protected]>
