aboutsummaryrefslogtreecommitdiff
path: root/gcc/testsuite/g++.dg/cpp2a/constexpr-new28.C
diff options
context:
space:
mode:
authorAndrew Pinski <andrew.pinski@oss.qualcomm.com>2025-10-14 10:36:03 -0700
committerAndrew Pinski <andrew.pinski@oss.qualcomm.com>2025-10-15 09:18:03 -0700
commit0a999da1c8842fd94706c13ced15a5205f497ecf (patch)
tree91f60a876e4d50b2b4469b80deefdc81869b17ce /gcc/testsuite/g++.dg/cpp2a/constexpr-new28.C
parent99af0f9078865269ae13367a25e2b156c8ccba77 (diff)
downloadgcc-master.zip
gcc-master.tar.gz
gcc-master.tar.bz2
debug_tree: print out clique/base for MEM_REF/TARGET_MEM_REFHEADtrunkmaster
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 <andrew.pinski@oss.qualcomm.com>
Diffstat (limited to 'gcc/testsuite/g++.dg/cpp2a/constexpr-new28.C')
0 files changed, 0 insertions, 0 deletions