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/95952] [8 Regression] gcc-8 bootstrap failure on powerpc64-linux Date: Fri, 17 Jul 2020 14:56:13 +0000 [thread overview] Message-ID: <bug-95952-4-AtXvzBkPDV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95952-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95952 --- Comment #17 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-8 branch has been updated by Will Schmidt <willschm@gcc.gnu.org>: https://gcc.gnu.org/g:eba1113dbdf4b1d0d88755b2538327a1d09837b3 commit r8-10362-geba1113dbdf4b1d0d88755b2538327a1d09837b3 Author: Will Schmidt <will_schmidt@vnet.ibm.com> Date: Mon Jul 13 13:38:17 2020 -0500 [PATCH] rs6000 improve handling of built-in initialization [PR95952] Handle a scenario with a combination of old hardware, gcc-8 and binutils where gcc will ICE during it's selftest. This ICE was exposed when the builtin processing for better #pragma support was added, where we no longer skip builtin initialization based on the current mask. Per the bug report and assorted debug, the ICE occurrs when building the gcc-8 branch on a 970* based system with an old binutils. (gcc-9 and newer is OK. binutils 2.34 is reported to allow success). The attached patch adds a clause to the builtin initialization to skip initialization of a builtin when the builtin mask is set but the icode value is zero. The subsequent assert check remains in place. 2020-07-13 Will Schmidt <will_schmidt@vnet.ibm.com> gcc/ChangeLog: PR target/95952 * config/rs6000/rs6000.c (altivec_init_builtins): Add continue clause to predicate builtin handling.
next prev parent reply other threads:[~2020-07-17 14:56 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-28 22:29 [Bug bootstrap/95952] New: [8.4.1 regression] " mikpelinux at gmail dot com 2020-06-29 10:43 ` [Bug bootstrap/95952] [8 Regression] " rguenth at gcc dot gnu.org 2020-06-29 13:33 ` [Bug target/95952] " wschmidt at gcc dot gnu.org 2020-06-29 16:13 ` willschm at gcc dot gnu.org 2020-06-29 16:33 ` bergner at gcc dot gnu.org 2020-06-29 16:59 ` bergner at gcc dot gnu.org 2020-06-29 17:23 ` mikpelinux at gmail dot com 2020-07-01 22:43 ` segher at gcc dot gnu.org 2020-07-01 23:28 ` mikpelinux at gmail dot com 2020-07-02 15:25 ` willschm at gcc dot gnu.org 2020-07-02 15:30 ` bergner at gcc dot gnu.org 2020-07-02 16:10 ` mikpelinux at gmail dot com 2020-07-13 22:04 ` willschm at gcc dot gnu.org 2020-07-13 22:06 ` willschm at gcc dot gnu.org 2020-07-14 16:41 ` mikpelinux at gmail dot com 2020-07-14 17:16 ` willschm at gcc dot gnu.org 2020-07-17 14:56 ` cvs-commit at gcc dot gnu.org [this message] 2020-07-21 14:37 ` willschm at gcc dot gnu.org 2020-07-21 14:38 ` willschm 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-95952-4-AtXvzBkPDV@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).