public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/110874] New: ice with -O2 with recent gcc Date: Wed, 02 Aug 2023 13:46:37 +0000 [thread overview] Message-ID: <bug-110874-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110874 Bug ID: 110874 Summary: ice with -O2 with recent gcc Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- Created attachment 55675 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55675&action=edit C source code The attached C code, when compiled by recent gcc trunk and -O2, does this: foundBugs $ ~/gcc/results/bin/gcc -c -w -O2 bug945.c buildData/keep/in.18686.c: In function ‘func_56’: buildData/keep/in.18686.c:1184:17: note: the ABI for passing parameters with 32-byte alignment has changed in GCC 4.6 gcc: internal compiler error: Segmentation fault signal terminated program cc1 Please submit a full bug report, with preprocessed source (by using -freport-bug). See <https://gcc.gnu.org/bugs/> for instructions. foundBugs $ -O1 is fine: foundBugs $ ~/gcc/results/bin/gcc -c -w -O1 bug945.c buildData/keep/in.18686.c: In function ‘func_56’: buildData/keep/in.18686.c:1184:17: note: the ABI for passing parameters with 32-byte alignment has changed in GCC 4.6 foundBugs $ Yesterday's compiler (g:01b0c36ba0c3bbe6) seems fine, but today's (g:0460c1221627938b), some 36 commits later, does not. I have a reduction running. It seems a side issue that -w was given to the compiler, but it still prints out notes about things that happened a long time ago (gcc 4.6).
next reply other threads:[~2023-08-02 13:46 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-02 13:46 dcb314 at hotmail dot com [this message] 2023-08-02 15:23 ` [Bug c/110874] " dcb314 at hotmail dot com 2023-08-02 15:58 ` [Bug middle-end/110874] [14 Regression] " pinskia at gcc dot gnu.org 2023-08-02 16:12 ` pinskia at gcc dot gnu.org 2023-08-02 16:59 ` pinskia at gcc dot gnu.org 2023-08-02 20:11 ` dcb314 at hotmail dot com 2023-08-02 20:14 ` dcb314 at hotmail dot com 2023-08-02 20:17 ` pinskia at gcc dot gnu.org 2023-08-02 20:32 ` pinskia at gcc dot gnu.org 2023-08-02 21:01 ` pinskia at gcc dot gnu.org 2023-08-02 21:09 ` pinskia at gcc dot gnu.org 2023-08-03 2:44 ` pinskia at gcc dot gnu.org 2023-08-03 6:59 ` pinskia at gcc dot gnu.org 2023-08-03 7:18 ` pinskia at gcc dot gnu.org 2023-08-03 22:49 ` pinskia at gcc dot gnu.org 2023-08-04 7:27 ` cvs-commit at gcc dot gnu.org 2023-08-04 7:27 ` pinskia 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-110874-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).