public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105485] ICE: Segmentation fault in pcrel-opt.md:get_insn_name() Date: Tue, 10 May 2022 12:23:11 +0000 [thread overview] Message-ID: <bug-105485-4-z6ZZdQNzX6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105485-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105485 Kewen Lin <linkw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Kewen Lin <linkw at gcc dot gnu.org> --- I was wrong, the local branch which I used as old bif support isn't the one before new bif support. The bisection showed it's a regression and started from r12-5752 (new bif support). By looking to the old bif support, I noticed that it's expected that this function won't be resolved, but we need to emit one error message during expanding. With old bif support, __builtin_vec_vslv is binded to the normal (primary) bif enum (bif code), it needs overloaded resolver (target hook) to resolve it into the overloaded bif enum; while with new bif support, __builtin_vec_vslv is binded to the overload bif enum, it needs overloaded resolver to resolve it into the one defined in rs6000-builtins.def (one instance of overloaded). In new bif support, rs6000_gimple_fold_builtin won't be able to handle the unresolved overloaded bif. Note that it doesn't in old bif support, but both primary and overloaded code shares the same table, so it's fine and no ICEs. With new bif support, overloaded bif code has its own table.
next prev parent reply other threads:[~2022-05-10 12:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-04 20:02 [Bug target/105485] New: " pthaugen at gcc dot gnu.org 2022-05-06 7:17 ` [Bug target/105485] " linkw at gcc dot gnu.org 2022-05-10 12:23 ` linkw at gcc dot gnu.org [this message] 2022-05-10 12:26 ` linkw at gcc dot gnu.org 2022-05-10 12:27 ` linkw at gcc dot gnu.org 2022-09-13 10:40 ` cvs-commit at gcc dot gnu.org 2022-09-21 5:07 ` cvs-commit at gcc dot gnu.org 2022-09-21 5:09 ` linkw 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-105485-4-z6ZZdQNzX6@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).