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/96127] ICE in extract_insn, at recog.c:2294 Date: Thu, 07 Dec 2023 08:45:53 +0000 [thread overview] Message-ID: <bug-96127-4-ounsb7LOhJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96127-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96127 --- Comment #6 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:0d79636b8d2c7f0da16fbf5f786993783a4389ff commit r14-6263-g0d79636b8d2c7f0da16fbf5f786993783a4389ff Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Dec 7 09:45:13 2023 +0100 testsuite: Fix up gcc.target/s390/pr96127.c test for modern C [PR96127] I've noticed this test regressed on s390x-linux with the addition of the switch to modern C patchset. Haven't tried to reproduce the ICE, but as it was a backend ICE and FE after warning used to add such casts before (now errors), I think this ought to keep the testcase testing what was intended before. 2023-12-07 Jakub Jelinek <jakub@redhat.com> PR target/96127 * gcc.target/s390/pr96127.c (c1): Add casts to long int *.
prev parent reply other threads:[~2023-12-07 8:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-09 7:50 [Bug target/96127] New: " marxin at gcc dot gnu.org 2020-07-09 7:52 ` [Bug target/96127] " marxin at gcc dot gnu.org 2020-07-17 7:36 ` cvs-commit at gcc dot gnu.org 2020-08-30 5:01 ` asolokha at gmx dot com 2021-09-02 16:59 ` redi at gcc dot gnu.org 2021-09-06 9:23 ` krebbel at gcc dot gnu.org 2023-12-03 18:23 ` jakub at gcc dot gnu.org 2023-12-07 8:45 ` 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-96127-4-ounsb7LOhJ@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).