aboutsummaryrefslogtreecommitdiff
path: root/libcc1
diff options
context:
space:
mode:
authorKewen Lin <linkw@linux.ibm.com>2020-11-08 20:35:21 -0600
committerKewen Lin <linkw@linux.ibm.com>2020-11-08 20:35:21 -0600
commitce4ae1f4893e322495c5d24b2f0e807a7f7cf92f (patch)
tree58d905f74ecd558b1615f53fd527df26467b630d /libcc1
parentfb95de7a11b8ac438857a02aaa0e1e50e9613f90 (diff)
downloadgcc-ce4ae1f4893e322495c5d24b2f0e807a7f7cf92f.zip
gcc-ce4ae1f4893e322495c5d24b2f0e807a7f7cf92f.tar.gz
gcc-ce4ae1f4893e322495c5d24b2f0e807a7f7cf92f.tar.bz2
ira: Recompute regstat as max_regno changes [PR97705]
As PR97705 shows, the commit r11-4637 caused some dumping comparison difference error on pass ira. It exposed one issue about the newly introduced function remove_scratches, which can increase the largest pseudo reg number if it succeeds, later some function will use the max_reg_num() to get the latest max_regno, when iterating the numbers we can access some data structures which are allocated as the previous max_regno, some out of array bound accesses can occur, the failure can be random since the values beyond the array could be random. This patch is to free/reinit/recompute the relevant data structures that is regstat_n_sets_and_refs and reg_info_p to ensure we won't access beyond some array bounds. Bootstrapped/regtested on powerpc64le-linux-gnu P9 and powerpc64-linux-gnu P8. gcc/ChangeLog: PR rtl-optimization/97705 * ira.c (ira): Refactor some regstat free/init/compute invocation into lambda function regstat_recompute_for_max_regno, and call it when max_regno increases as remove_scratches succeeds.
Diffstat (limited to 'libcc1')
0 files changed, 0 insertions, 0 deletions