https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115208
Bug ID: 115208 Summary: [15 Regression] Memory consumption get extremely high after r15-809 Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: haochen.jiang at intel dot com Target Milestone: --- I currently got some testcase fail on i686 target. New failures: FAIL: gcc.target/i386/avx-1.c (test for excess errors) FAIL: gcc.target/i386/sse-13.c (test for excess errors) FAIL: gcc.target/i386/sse-23.c (test for excess errors) FAIL: gcc.target/i386/sse-24.c (test for excess errors) FAIL: gcc.target/i386/sse-25.c (test for excess errors) FAIL: gcc.target/i386/sse-26.c (test for excess errors) >From my investigation, it happened after the commit series r15-797 to r15-809. After those commits, the memory consumption got very high. I ran with: make check-gcc RUNTESTFLAGS="i386.exp=avx-1.c --target_board='unix{-m32}'" Before those commits, the memory usage: Memory usage summary: heap total: 245591, heap peak: 205651, stack peak: 13824 total calls total memory failed calls malloc| 402 238998 0 realloc| 14 5416 0 (nomove:7, dec:0, free:0) calloc| 6 1177 0 free| 224 57705 After those commits, the memory usage: Memory usage summary: heap total: 17691252434, heap peak: 7691866921, stack peak: 51056 total calls total memory failed calls malloc| 69614075 15426859093 0 realloc| 260731 17538362 0 (nomove:88951, dec:19349, free:0) calloc| 11132073 2246854979 0 free| 81105599 9997315310 Since i686 target gets very limited memory, it crashed those targets.