aboutsummaryrefslogtreecommitdiff
path: root/gcc/hash-map-tests.c
diff options
context:
space:
mode:
authorRichard Sandiford <richard.sandiford@arm.com>2021-04-14 20:06:44 +0100
committerRichard Sandiford <richard.sandiford@arm.com>2021-04-14 20:06:44 +0100
commit1fce5932a3af575cd02c1d2b786dd1b39b922ebe (patch)
tree5e7a09f47f78fcdeb434e466f53f402cad343392 /gcc/hash-map-tests.c
parent00a2774923c1dc5666cd26bb9b8c37b1b7dd689d (diff)
downloadgcc-1fce5932a3af575cd02c1d2b786dd1b39b922ebe.zip
gcc-1fce5932a3af575cd02c1d2b786dd1b39b922ebe.tar.gz
gcc-1fce5932a3af575cd02c1d2b786dd1b39b922ebe.tar.bz2
Better const_vector printing
Looking at PR99929 showed that we weren't dumping enough information about variable-length CONST_VECTORs. Something like: (const_vector:VNx4SI [(const_int 1) (const_int 0)]) could be either: (a) 1, 0, 1, 0, repeating (b) 1 followed by all zeros This patch adds more information to the dumps. There are four cases: (a) above: (const_vector:VNx4SI repeat [ (const_int 1) (const_int 0) ]) (b) above: (const_vector:VNx4SI [ (const_int 1) repeat [ (const_int 0) ] ]) a single stepped sequence: (const_vector:VNx4SI [ (const_int 0) stepped [ (const_int 1) (const_int 2) ] ]) interleaved stepped sequences: (const_vector:VNx4SI [ (const_int 0) (const_int 40) stepped (interleave 2) [ (const_int 1) (const_int 41) (const_int 2) (const_int 42) ] ]) There are probably better syntaxes, but hopefully this is at least an improvement on the status quo. gcc/ * print-rtl.c (rtx_writer::print_rtx_operand_codes_E_and_V): Print more information about variable-length CONST_VECTORs.
Diffstat (limited to 'gcc/hash-map-tests.c')
0 files changed, 0 insertions, 0 deletions