public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107497] [13 regression] ICE during bootstrap after r13-3595-g7b1cdca6d6d594 Date: Tue, 01 Nov 2022 16:54:34 +0000 [thread overview] Message-ID: <bug-107497-4-7WT5Snx6wq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107497-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107497 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-11-01 Host|powerpc64-linux-gnu, |powerpc64-linux-gnu, |powerpc64le-linux-gnu |powerpc64le-linux-gnu | |x86_64-linux-gnu Target|powerpc64-linux-gnu, |powerpc64-linux-gnu, |powerpc64le-linux-gnu |powerpc64le-linux-gnu | |x86_64-linux-gnu Ever confirmed|0 |1 Build|powerpc64-linux-gnu, |powerpc64-linux-gnu, |powerpc64le-linux-gnu |powerpc64le-linux-gnu | |x86_64-linux-gnu Status|UNCONFIRMED |NEW --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Looks like it also fails on x86_64: https://gcc.gnu.org/pipermail/gcc-testresults/2022-November/771026.html https://gcc.gnu.org/pipermail/gcc-testresults/2022-November/771027.html I suspect building with mpfr/mpc/gmp in the source tree is definitely a good test of the compiler, especially with floating point too :).
next prev parent reply other threads:[~2022-11-01 16:54 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-01 16:35 [Bug tree-optimization/107497] New: " seurer at gcc dot gnu.org 2022-11-01 16:51 ` [Bug tree-optimization/107497] " pinskia at gcc dot gnu.org 2022-11-01 16:54 ` pinskia at gcc dot gnu.org [this message] 2022-11-01 16:59 ` seurer at gcc dot gnu.org 2022-11-01 17:07 ` mpolacek at gcc dot gnu.org 2022-11-01 17:29 ` amacleod at redhat dot com 2022-11-01 18:02 ` cvs-commit at gcc dot gnu.org 2022-11-01 18:46 ` i.nixman at autistici dot org 2022-11-01 18:47 ` amacleod at redhat dot com 2022-11-01 18:50 ` i.nixman at autistici dot org 2022-11-01 19:25 ` seurer at gcc dot gnu.org 2022-11-01 21:15 ` i.nixman at autistici dot org 2022-11-01 21:25 ` pinskia 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-107497-4-7WT5Snx6wq@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).