public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99279] New: ICE in rs6000_init_builtins when compiling using -mcpu=440 Date: Fri, 26 Feb 2021 00:15:58 +0000 [thread overview] Message-ID: <bug-99279-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99279 Bug ID: 99279 Summary: ICE in rs6000_init_builtins when compiling using -mcpu=440 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: bergner at gcc dot gnu.org Target Milestone: --- The following ICEs after my commit below: commit 77ef995c1fbcab76a2a69b9f4700bcfd005d8e62 (HEAD -> master, origin/master, origin/HEAD) Author: Peter Bergner <bergner@linux.ibm.com> AuthorDate: Tue Feb 23 17:16:10 2021 -0600 Commit: Peter Bergner <bergner@linux.ibm.com> CommitDate: Tue Feb 23 17:16:10 2021 -0600 rs6000: Add support for compatibility built-ins [bergner@makalu-lp1 MMA]$ cat simple.c int main (void) { return 0; } [bergner@makalu-lp1 MMA]$ gcc -S -mcpu=440 -m32 simple.c <built-in>: internal compiler error: in rs6000_init_builtins, at config/rs6000/rs6000-call.c:13471 0x111e7183 rs6000_init_builtins() /home/bergner/gcc/gcc-fsf-mainline-mma-compat-base/gcc/config/rs6000/rs6000-call.c:13471 0x1030e037 c_define_builtins /home/bergner/gcc/gcc-fsf-mainline-mma-compat-base/gcc/c-family/c-common.c:4013
next reply other threads:[~2021-02-26 0:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-26 0:15 bergner at gcc dot gnu.org [this message] 2021-02-26 0:18 ` [Bug target/99279] " bergner at gcc dot gnu.org 2021-02-26 3:36 ` cvs-commit at gcc dot gnu.org 2021-02-26 3:42 ` bergner at gcc dot gnu.org 2021-03-10 23:48 ` cvs-commit at gcc dot gnu.org 2021-03-11 0:05 ` bergner 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-99279-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).