public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "christian.holme at med dot uni-goettingen.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/100924] New: GCC 11.1.1 internal compiler error: segfault at VLA function definition Date: Sat, 05 Jun 2021 11:12:53 +0000 [thread overview] Message-ID: <bug-100924-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100924 Bug ID: 100924 Summary: GCC 11.1.1 internal compiler error: segfault at VLA function definition Product: gcc Version: 11.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: christian.holme at med dot uni-goettingen.de Target Milestone: --- Created attachment 50949 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50949&action=edit Failing source Hey, when compiling the attached vlatest_min.c, I encounter an internal compiler error: segmentation fault with gcc 11.1.1. The precise version information (collected with gcc -v) can be found in the attached compilation log. With gcc master from 2021-06-02 it compiles without error. Changing optimization level from -O3 to -O1 also removes the segfault, but -O2 still segfaults. I have also attached the compiler output for both gcc 11 and 12 (master) and the preprocessed files in both cases. Since a fix for it exists on master, I am submitting this bug report in the hopes that it will make it easier to fix in the next release of gcc 11. Best regards
next reply other threads:[~2021-06-05 11:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-05 11:12 christian.holme at med dot uni-goettingen.de [this message] 2021-06-05 11:13 ` [Bug c/100924] " christian.holme at med dot uni-goettingen.de 2021-06-05 11:14 ` christian.holme at med dot uni-goettingen.de 2021-06-05 11:14 ` christian.holme at med dot uni-goettingen.de 2021-06-07 10:23 ` rguenth at gcc dot gnu.org 2021-06-07 13:25 ` jakub at gcc dot gnu.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-100924-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).