diff options
| author | Aldy Hernandez <aldyh@redhat.com> | 2023-01-19 18:42:30 +0100 |
|---|---|---|
| committer | Aldy Hernandez <aldyh@redhat.com> | 2023-04-26 11:45:22 +0200 |
| commit | 1a8087c7d1cb3ca1daa87a61766923bad0143700 (patch) | |
| tree | bed9b2f86816f679a277e803eb909fdf1c623338 /gcc/value-range-pretty-print.cc | |
| parent | 04e5ddf8a313e85348a05c27708c845cc45e2e83 (diff) | |
| download | gcc-1a8087c7d1cb3ca1daa87a61766923bad0143700.zip gcc-1a8087c7d1cb3ca1daa87a61766923bad0143700.tar.gz gcc-1a8087c7d1cb3ca1daa87a61766923bad0143700.tar.bz2 | |
Replace ad-hoc value_range dumpers with irange::dump.
This causes a regression in gcc.c-torture/unsorted/dump-noaddr.c.
The test is asserting that two dumps are identical, but they are not
because irange dumps the type which varies between runs:
< VR [irange] void (*<T3dc>) (int) [1, +INF]
> VR [irange] void (*<T3da>) (int) [1, +INF]
I have changed the pretty printer for irange types to pass TDF_NOUID,
thus avoiding this problem.
gcc/ChangeLog:
* ipa-prop.cc (ipa_print_node_jump_functions_for_edge): Use
vrange::dump instead of ad-hoc dumper.
* tree-ssa-strlen.cc (dump_strlen_info): Same.
* value-range-pretty-print.cc (visit): Pass TDF_NOUID to
dump_generic_node.
Diffstat (limited to 'gcc/value-range-pretty-print.cc')
| -rw-r--r-- | gcc/value-range-pretty-print.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/value-range-pretty-print.cc b/gcc/value-range-pretty-print.cc index a11c5a6..8d47d80 100644 --- a/gcc/value-range-pretty-print.cc +++ b/gcc/value-range-pretty-print.cc @@ -56,7 +56,7 @@ vrange_printer::visit (const irange &r) const pp_string (pp, "UNDEFINED"); return; } - dump_generic_node (pp, r.type (), 0, TDF_NONE, false); + dump_generic_node (pp, r.type (), 0, TDF_NONE | TDF_NOUID, false); pp_character (pp, ' '); if (r.varying_p ()) { |