aboutsummaryrefslogtreecommitdiff
path: root/gcc/doc
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2023-12-08 08:29:44 +0100
committerJakub Jelinek <jakub@redhat.com>2023-12-08 08:29:44 +0100
commit39a1ab9c33b6067b1cc843408886e7ba709fbb62 (patch)
tree6d172772f3e505bc16a25f7d601874aea327d4f0 /gcc/doc
parent642190b4160da74c5d382c1cea71c6e617c557cb (diff)
downloadgcc-39a1ab9c33b6067b1cc843408886e7ba709fbb62.zip
gcc-39a1ab9c33b6067b1cc843408886e7ba709fbb62.tar.gz
gcc-39a1ab9c33b6067b1cc843408886e7ba709fbb62.tar.bz2
Add IntegerRange for -param=min-nondebug-insn-uid= and fix vector growing in LRA and vec [PR112411]
As documented, --param min-nondebug-insn-uid= is very useful in debugging -fcompare-debug issues in RTL dumps, without it it is really hard to find differences. With it, DEBUG_INSNs generally use low INSN_UIDs (1+) and non-DEBUG_INSNs use INSN_UIDs from the parameter up. For good results, the parameter should be larger than the number of DEBUG_INSNs in all or at least problematic functions, so I typically use --param min-nondebug-insn-uid=10000 or --param min-nondebug-insn-uid=1000. The PR is about using --param min-nondebug-insn-uid=2147483647 or similar behavior can be achieved with that minus some epsilon, INSN_UIDs for the non-debug insns then wrap around and as they are signed, all kinds of things break. Obviously, that can happen even without that option, but functions containing more than 2147483647 insns usually don't compile much earlier due to getting out of memory. As it is a debugging option, I'd prefer not to impose any drastically small limits on it because if a function has a lot of DEBUG_INSNs, it is useful to start still above them, otherwise the allocation of uids will DTRT even for DEBUG_INSNs but there will be then differences in non-DEBUG_INSN allocations. So, the following patch uses 0x40000000 limit, half the maximum amount for DEBUG_INSNs and half for non-DEBUG_INSNs, it will still result in very unlikely overflows in real world. Note, using large min-nondebug-insn-uid is very expensive for compile time memory and compile time, because DF as well as various RTL passes use arrays indexed by INSN_UIDs, e.g. LRA with sizeof (void *) elements, ditto df (df->insns). Now, in LRA I've ran into ICEs already with --param min-nondebug-insn-uid=0x2aaaaaaa on 64-bit host. It uses a custom vector management and wants to grow allocation 1.5x when growing, but all this computation is done in int, so already 0x2aaaaaab * 3 / 2 + 1 overflows to negative value. And unlike vec.cc growing which also uses unsigned int type for the above (and the + 1 is not there), it also doesn't make sure if there is an overflow that it allocates at least as much as needed, vec.cc does if ... else /* Grow slower when large. */ alloc = (alloc * 3 / 2); /* If this is still too small, set it to the right size. */ if (alloc < desired) alloc = desired; so even if there is overflow during the * 1.5 computation, but desired is still representable in the range of the alloced counter (31-bits in both vec.h and LRA), it doesn't grow exponentially but at least works for the current value. The patch now uses there lra_insn_recog_data_len = index * 3U / 2; if (lra_insn_recog_data_len <= index) lra_insn_recog_data_len = index + 1; basically do what vec.cc does. I thought we could do better for both vec.cc and LRA on 64-bit hosts even without growing the allocated counters, but now that I look at it again, perhaps we can't. The above overflows already with original alloc or lra_insn_recog_data_len 0x55555556, where 0x5555555 * 3U / 2 is still 0x7fffffff and so representable in the 32-bit, but 0x55555556 * 3U / 2 is 1. I thought that we could use alloc * (size_t) 3 / 2 so that on 64-bit hosts it wouldn't overflow that quickly, but 0x55555556 * (size_t) 3 / 2 there is 0x80000001 which is still ok in unsigned, but given that vec.h then stores the counter into unsigned m_alloc:31; bit-field, it is too much. With the lra.cc change, one can actually compile simple function with -O0 on 64-bit host with --param min-nondebug-insn-uid=0x40000000 (i.e. the new limit), but already needed quite a big part of my 32GB RAM + 24GB swap. The patch adds a dg-skip-if for that case though, because such option is way too much for 32-bit hosts even at -O0 and empty function, and with -O3 on a longer function it is too much for average 64-bit host as well. Without the dg-skip-if I got on 64-bit host: cc1: out of memory allocating 571230784744 bytes after a total of 2772992 bytes and cc1: out of memory allocating 1388 bytes after a total of 2002944 bytes on 32-bit host. A test requiring more than 532GB of RAM on 64-bit hosts is just too much for our testsuite. 2023-12-08 Jakub Jelinek <jakub@redhat.com> PR middle-end/112411 * params.opt (-param=min-nondebug-insn-uid=): Add IntegerRange(0, 1073741824). * lra.cc (check_and_expand_insn_recog_data): Use 3U rather than 3 in * 3 / 2 computation and if the result is smaller or equal to index, use index + 1. * gcc.dg/params/blocksort-part.c: Add dg-skip-if for --param min-nondebug-insn-uid=1073741824.
Diffstat (limited to 'gcc/doc')
0 files changed, 0 insertions, 0 deletions