diff options
author | Richard Sandiford <richard.sandiford@arm.com> | 2021-04-14 20:06:45 +0100 |
---|---|---|
committer | Richard Sandiford <richard.sandiford@arm.com> | 2021-04-14 20:06:45 +0100 |
commit | a87d3f964df31d4fbceb822c6d293e85c117d992 (patch) | |
tree | 5b0d160928a75af3bbf9d3e0895955f34c0e6373 /gcc/d/ChangeLog | |
parent | 1fce5932a3af575cd02c1d2b786dd1b39b922ebe (diff) | |
download | gcc-a87d3f964df31d4fbceb822c6d293e85c117d992.zip gcc-a87d3f964df31d4fbceb822c6d293e85c117d992.tar.gz gcc-a87d3f964df31d4fbceb822c6d293e85c117d992.tar.bz2 |
Check for matching CONST_VECTOR encodings [PR99929]
PR99929 is one of those “how did we get away with this for so long”
bugs: the equality routines weren't checking whether two variable-length
CONST_VECTORs had the same encoding. This meant that:
{ 1, 0, 0, 0, 0, 0, ... }
would appear to be equal to:
{ 1, 0, 1, 0, 1, 0, ... }
since both are represented using the elements { 1, 0 }.
gcc/
PR rtl-optimization/99929
* rtl.h (same_vector_encodings_p): New function.
* cse.c (exp_equiv_p): Check that CONST_VECTORs have the same encoding.
* cselib.c (rtx_equal_for_cselib_1): Likewise.
* jump.c (rtx_renumbered_equal_p): Likewise.
* lra-constraints.c (operands_match_p): Likewise.
* reload.c (operands_match_p): Likewise.
* rtl.c (rtx_equal_p_cb, rtx_equal_p): Likewise.
gcc/testsuite/
* gcc.target/aarch64/sve/pr99929_1.c: New file.
* gcc.target/aarch64/sve/pr99929_2.c: Likewise.
Diffstat (limited to 'gcc/d/ChangeLog')
0 files changed, 0 insertions, 0 deletions