public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99279] ICE in rs6000_init_builtins when compiling using -mcpu=440 Date: Fri, 26 Feb 2021 03:36:39 +0000 [thread overview] Message-ID: <bug-99279-4-bDEONBKG6s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99279-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99279 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Peter Bergner <bergner@gcc.gnu.org>: https://gcc.gnu.org/g:0159535adb0e7400f2c6922f14a7602f6b90cf69 commit r11-7415-g0159535adb0e7400f2c6922f14a7602f6b90cf69 Author: Peter Bergner <bergner@linux.ibm.com> Date: Thu Feb 25 21:35:28 2021 -0600 rs6000: Fix ICE in rs6000_init_builtins when compiling with -mcpu=440 [PR99279] The initialization of compat builtins assumes the builtin we are creating a compatible builtin for exists and ICEs if it doesn't. However, there are valid reasons why some builtins are disabled for a particular compile. In this case, the MMA builtins are disabled for -mcpu=440 (and other cpus), so instead of ICEing, we should just skip adding the MMA compat builtin. 2021-02-25 Peter Bergner <bergner@linux.ibm.com> gcc/ PR target/99279 * config/rs6000/rs6000-call.c (rs6000_init_builtins): Replace assert with an "if" test.
next prev parent reply other threads:[~2021-02-26 3:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-26 0:15 [Bug target/99279] New: " bergner at gcc dot gnu.org 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 [this message] 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-bDEONBKG6s@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).