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 jit/107999] [13 Regression] jit.dg/test-error-array-bounds.c now fails because [-Warray-bounds] was updated to [-Warray-bounds=] in error messages after r13-4410-g7c01d029fca669263b9c2 Date: Thu, 02 Mar 2023 22:53:12 +0000 [thread overview] Message-ID: <bug-107999-4-OlNOK1Gshb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107999-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107999 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>: https://gcc.gnu.org/g:6b432c0f777ab9b8436fb07f71de6ea4d259b869 commit r13-6425-g6b432c0f777ab9b8436fb07f71de6ea4d259b869 Author: Guillaume Gomez <guillaume1.gomez@gmail.com> Date: Thu Mar 2 17:52:07 2023 -0500 jit, testsuite: fix a failing test by updating its error string [PR107999] gcc/testsuite/ChangeLog: PR jit/107999 * jit.dg/test-error-array-bounds.c: Update test. Signed-off-by: Guillaume Gomez <guillaume1.gomez@gmail.com>
next prev parent reply other threads:[~2023-03-02 22:53 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-07 0:40 [Bug jit/107999] New: test-error-array-bounds.c now fails because [-Warray-bounds] was updated to [-Warray-bounds=] in error messages bouanto at zoho dot com 2022-12-07 0:53 ` [Bug testsuite/107999] [13 Regression] test-error-array-bounds.c now fails because [-Warray-bounds] was updated to [-Warray-bounds=] in error messages after r13-4410-g7c01d029fca669263b9c2 pinskia at gcc dot gnu.org 2023-01-23 23:43 ` [Bug jit/107999] [13 Regression] jit.dg/test-error-array-bounds.c " bouanto at zoho dot com 2023-02-21 13:41 ` rguenth at gcc dot gnu.org 2023-03-02 22:53 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-02 22:57 ` dmalcolm 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-107999-4-OlNOK1Gshb@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).