public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111329] [14 regression] gcc.dg/analyzer/out-of-bounds-diagram-1-debug.c fails after r14-3745-g4f4fa2501186e4 Date: Fri, 08 Sep 2023 09:28:17 +0000 [thread overview] Message-ID: <bug-111329-4-gInqNDP5pt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111329-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111329 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2023-09-08 Ever confirmed|0 |1 --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 55854 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55854&action=edit gcc14-pr111329.patch So far only very lightly tested patch (tested that the test FAILs in bootstrapped build, applied patch, make -j32 in the stage3 directory, make check for the test again, which now PASSes). Had to put the out of line function into wide-int-print.cc rather than pretty-print.cc, because otherwise e.g. modula2 doesn't link.
next prev parent reply other threads:[~2023-09-08 9:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-07 18:39 [Bug other/111329] New: " seurer at gcc dot gnu.org 2023-09-07 18:53 ` [Bug other/111329] " jakub at gcc dot gnu.org 2023-09-07 19:07 ` [Bug analyzer/111329] " dmalcolm at gcc dot gnu.org 2023-09-07 19:23 ` seurer at gcc dot gnu.org 2023-09-07 19:46 ` jakub at gcc dot gnu.org 2023-09-08 5:20 ` rsandifo at gcc dot gnu.org 2023-09-08 9:28 ` jakub at gcc dot gnu.org [this message] 2023-09-11 9:10 ` [Bug middle-end/111329] " cvs-commit at gcc dot gnu.org 2023-09-11 9:13 ` jakub 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-111329-4-gInqNDP5pt@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).