public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/115208] New: [15 Regression] Memory consumption get extremely high after r15-809
@ 2024-05-24  6:35 haochen.jiang at intel dot com
  2024-05-24  6:39 ` [Bug middle-end/115208] " haochen.jiang at intel dot com
                   ` (11 more replies)
  0 siblings, 12 replies; 13+ messages in thread
From: haochen.jiang at intel dot com @ 2024-05-24  6:35 UTC (permalink / raw)
  To: gcc-bugs

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.

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2024-05-26 12:43 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-24  6:35 [Bug middle-end/115208] New: [15 Regression] Memory consumption get extremely high after r15-809 haochen.jiang at intel dot com
2024-05-24  6:39 ` [Bug middle-end/115208] " haochen.jiang at intel dot com
2024-05-24  6:41 ` [Bug tree-optimization/115208] " pinskia at gcc dot gnu.org
2024-05-24  7:39 ` rguenth at gcc dot gnu.org
2024-05-24 13:22 ` pinskia at gcc dot gnu.org
2024-05-24 14:08 ` ro at gcc dot gnu.org
2024-05-25  2:16 ` [Bug tree-optimization/115208] [15 Regression] Memory consumption get extremely high after r15-807-gfae5e6a4dfcf92 sjames at gcc dot gnu.org
2024-05-25 15:08 ` schwab@linux-m68k.org
2024-05-25 16:38 ` amacleod at redhat dot com
2024-05-25 19:46 ` slyfox at gcc dot gnu.org
2024-05-26  1:46 ` cvs-commit at gcc dot gnu.org
2024-05-26  9:12 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-26 12:43 ` haochen.jiang at intel dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).