public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/115227] New: [15 Regression] i686-linux fails frequently with cc1: out of memory allocating x bytes after a total of ~4GB Date: Sat, 25 May 2024 14:49:55 +0000 [thread overview] Message-ID: <bug-115227-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115227 Bug ID: 115227 Summary: [15 Regression] i686-linux fails frequently with cc1: out of memory allocating x bytes after a total of ~4GB Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: slyfox at gcc dot gnu.org Target Milestone: --- Created attachment 58286 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58286&action=edit bug.c.c.xz Initially noticed on libepoxy, doxygen, llvm, p11-kit. They all fail to build by 32-bit gcc-15. The symptoms are similar: 4GB limit is hit and `gcc` fails on allocation. Attached preprocessed and compressed example of libepoxy: $ gcc-15 -std=gnu99 -fno-strict-aliasing -fvisibility=hidden -c bug.c.c -o bug.o -O2 cc1: out of memory allocating 65536 bytes after a total of 3774660608 bytes For comparison gcc-13 is able to survive: $ gcc-13 -std=gnu99 -fno-strict-aliasing -fvisibility=hidden -c bug.c.c -o bug.o -O2 <ok> $ gcc-15 -v Using built-in specs. COLLECT_GCC=/<<NIX>>/gcc-15.0.0/bin/gcc COLLECT_LTO_WRAPPER=/<<NIX>>/gcc-15.0.0/libexec/gcc/i686-unknown-linux-gnu/15.0.0/lto-wrapper Target: i686-unknown-linux-gnu Configured with: ../source/configure --prefix=/<<NIX>>/gcc-15.0.0 --with-gmp-include=/<<NIX>>/gmp-6.3.0-dev/include --with-gmp-lib=/<<NIX>>/gmp-6.3.0/lib --with-mpfr-include=/<<NIX>>/mpfr-4.2.1-dev/include --with-mpfr-lib=/<<NIX>>/mpfr-4.2.1/lib --with-mpc=/<<NIX>>/libmpc-1.3.1 --with-native-system-header-dir=/<<NIX>>/glibc-2.39-52-dev/include --with-build-sysroot=/ --with-gxx-include-dir=/<<NIX>>/gcc-15.0.0/include/c++/15.0.0/ --program-prefix= --enable-lto --disable-libstdcxx-pch --without-included-gettext --with-system-zlib --enable-checking=release --enable-static --enable-languages=c,c++ --disable-multilib --enable-plugin --disable-libcc1 --with-isl=/<<NIX>>/isl-0.20 --disable-bootstrap --with-arch=i686 --build=i686-unknown-linux-gnu --host=i686-unknown-linux-gnu --target=i686-unknown-linux-gnu Thread model: posix Supported LTO compression algorithms: zlib gcc version 15.0.0 99999999 (experimental) (GCC)
next reply other threads:[~2024-05-25 14:49 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-25 14:49 slyfox at gcc dot gnu.org [this message] 2024-05-25 15:08 ` [Bug c/115227] " schwab@linux-m68k.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-115227-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).