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/105485] ICE: Segmentation fault in pcrel-opt.md:get_insn_name() Date: Tue, 13 Sep 2022 10:40:27 +0000 [thread overview] Message-ID: <bug-105485-4-l7wl37jbmN@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 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:94504c9ae157db937a2e62d533a36d56598f3c09 commit r13-2642-g94504c9ae157db937a2e62d533a36d56598f3c09 Author: Kewen.Lin <linkw@gcc.gnu.org> Date: Tue Sep 13 04:13:59 2022 -0500 rs6000: Handle unresolved overloaded builtin [PR105485] PR105485 exposes that new builtin function framework doesn't handle unresolved overloaded builtin function well. With new builtin function support, we don't have builtin info for any overloaded rs6000_gen_builtins enum, since they are expected to be resolved to one specific instance. So when function rs6000_gimple_fold_builtin faces one unresolved overloaded builtin, the access for builtin info becomes out of bound and gets ICE then. We should not try to fold one unresolved overloaded builtin there and as the previous support we should emit one error message during expansion phase like "unresolved overload for builtin ...". PR target/105485 gcc/ChangeLog: * config/rs6000/rs6000-builtin.cc (rs6000_gimple_fold_builtin): Add the handling for unresolved overloaded builtin function. (rs6000_expand_builtin): Likewise. gcc/testsuite/ChangeLog: * g++.target/powerpc/pr105485.C: New test.
next prev parent reply other threads:[~2022-09-13 10:40 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 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 [this message] 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-l7wl37jbmN@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).