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/103622] [12 Regression] ICE: Segmentation fault (in altivec_resolve_new_overloaded_builtin) Date: Wed, 05 Jan 2022 22:54:56 +0000 [thread overview] Message-ID: <bug-103622-4-qg1mZdHvja@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103622-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103622 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by William Schmidt <wschmidt@gcc.gnu.org>: https://gcc.gnu.org/g:4ec62dbafe0cb3b79cc635dfb964ef6a7ccc2d40 commit r12-6275-g4ec62dbafe0cb3b79cc635dfb964ef6a7ccc2d40 Author: Bill Schmidt <wschmidt@linux.ibm.com> Date: Wed Jan 5 16:53:29 2022 -0600 rs6000: Skip overload instances with uninitialized fntype (PR103622) 2022-01-05 Bill Schmidt <wschmidt@linux.ibm.com> gcc/ PR target/103622 * config/rs6000/rs6000-c.c (altivec_resolve_overloaded_builtin): Skip over instances with undefined function types.
next prev parent reply other threads:[~2022-01-05 22:54 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-09 7:15 [Bug target/103622] New: " asolokha at gmx dot com 2021-12-09 9:50 ` [Bug target/103622] " linkw at gcc dot gnu.org 2021-12-09 11:48 ` linkw at gcc dot gnu.org 2021-12-09 14:03 ` linkw at gcc dot gnu.org 2021-12-09 21:24 ` wschmidt at gcc dot gnu.org 2021-12-09 21:37 ` wschmidt at gcc dot gnu.org 2021-12-12 16:44 ` [Bug target/103622] [12 Regression] " wschmidt at gcc dot gnu.org 2021-12-13 13:54 ` wschmidt at gcc dot gnu.org 2021-12-13 14:01 ` wschmidt at gcc dot gnu.org 2021-12-13 16:16 ` wschmidt at gcc dot gnu.org 2021-12-15 2:53 ` linkw at gcc dot gnu.org 2022-01-05 22:54 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-06 1:41 ` wschmidt 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-103622-4-qg1mZdHvja@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).