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 middle-end/112406] [14 Regression] Several SPECCPU 2017 benchmarks fail with on internal compiler error: in expand_insn, at optabs.cc:8305 after g:01c18f58d37865d5f3bbe93e666183b54ec608c7 Date: Sun, 03 Dec 2023 19:04:36 +0000 [thread overview] Message-ID: <bug-112406-4-dtrYZfOG4k@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112406-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112406 --- Comment #25 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:4c0dc30099d39ef6d1b6c8c81418c726aa660768 commit r14-6096-g4c0dc30099d39ef6d1b6c8c81418c726aa660768 Author: Jakub Jelinek <jakub@redhat.com> Date: Sun Dec 3 20:03:27 2023 +0100 testsuite: Fix up gcc.target/aarch64/pr112406.c for modern C [PR112406] On Fri, Nov 17, 2023 at 02:04:01PM +0100, Robin Dapp wrote: > > Yes, your version is also OK. > > The attached was bootstrapped and regtested on aarch64, x86 and > regtested on riscv. Going to commit it later unless somebody objects. Unfortunately the aarch64/pr112406.c was reduced too much and is rejected since the switch to modern C patchset. The following patch fixes that, I've verified the testcase before/after the changes still ICEs in r14-5563 and doesn't with r14-5564 and after the changes compiles fine with even latest trunk. Everything admittedly with a cross-compiler, but that shouldn't change anything. Note, one of the modern C changes is that at least when people use cvise/creduce/delta scripts which ensure no further errors are introduced during the reduction then expected originally such reductions will not appear anymore. 2023-12-03 Jakub Jelinek <jakub@redhat.com> PR middle-end/112406 * gcc.target/aarch64/pr112406.c (MagickPixelPacket): Add missing semicolon. (GetImageChannelMoments_image): Avoid using implicit int. (SetMagickPixelPacket): Use void return type instead of implicit int. (GetImageChannelMoments): Likewise. Use __builtin_atan instead of atan.
prev parent reply other threads:[~2023-12-03 19:04 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-06 11:20 [Bug middle-end/112406] New: [14 Regression] Several SPECCPU 2017 benchmarks fail with internal compiler error: in expand_insn, at optabs.cc:8305 tnfchris at gcc dot gnu.org 2023-11-06 13:11 ` [Bug middle-end/112406] [14 Regression] Several SPECCPU 2017 benchmarks fail with LTO on " rguenth at gcc dot gnu.org 2023-11-07 11:23 ` tnfchris at gcc dot gnu.org 2023-11-07 21:38 ` cvs-commit at gcc dot gnu.org 2023-11-08 7:00 ` rguenth at gcc dot gnu.org 2023-11-08 7:02 ` tnfchris at gcc dot gnu.org 2023-11-08 10:24 ` tnfchris at gcc dot gnu.org 2023-11-08 10:25 ` [Bug middle-end/112406] [14 Regression] Several SPECCPU 2017 benchmarks fail with on internal compiler error: in expand_insn, at optabs.cc:8305 after g:01c18f58d37865d5f3bbe93e666183b54ec608c7 tnfchris at gcc dot gnu.org 2023-11-08 10:40 ` rdapp at gcc dot gnu.org 2023-11-08 11:06 ` rdapp at gcc dot gnu.org 2023-11-08 11:24 ` rdapp at gcc dot gnu.org 2023-11-08 15:50 ` tnfchris at gcc dot gnu.org 2023-11-08 15:54 ` rdapp at gcc dot gnu.org 2023-11-17 20:35 ` cvs-commit at gcc dot gnu.org 2023-11-20 9:23 ` cvs-commit at gcc dot gnu.org 2023-11-21 4:45 ` tnfchris at gcc dot gnu.org 2023-11-21 7:38 ` rdapp at gcc dot gnu.org 2023-11-21 9:07 ` tnfchris at gcc dot gnu.org 2023-11-21 9:33 ` rdapp at gcc dot gnu.org 2023-11-21 10:29 ` rdapp at gcc dot gnu.org 2023-11-21 10:51 ` tnfchris at gcc dot gnu.org 2023-11-21 11:22 ` rdapp at gcc dot gnu.org 2023-11-21 11:40 ` rdapp at gcc dot gnu.org 2023-11-21 20:11 ` cvs-commit at gcc dot gnu.org 2023-11-23 12:08 ` tnfchris at gcc dot gnu.org 2023-12-02 19:20 ` pinskia at gcc dot gnu.org 2023-12-03 19:04 ` cvs-commit at gcc dot gnu.org [this message]
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-112406-4-dtrYZfOG4k@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).