public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: jit@gcc.gnu.org,	gcc-patches@gcc.gnu.org
Cc: Martin Sebor <msebor@redhat.com>,	David Malcolm <dmalcolm@redhat.com>
Subject: [committed] jit: update test suite for change to -Warray-bounds
Date: Sun, 01 Jan 2017 00:00:00 -0000	[thread overview]
Message-ID: <1511385398-37122-1-git-send-email-dmalcolm@redhat.com> (raw)

jit.dg/test-error-array-bounds.c is a test of how libgccjit
handles errors coming from the middle-end, using -Warray-bounds as
an example.

It started failing as of r254830 (aka 987b3316c4e7c908e3c7d2151c20971f9707ad66),
due to that commit changing the wording of the message.

This commit fixes the jit testcase by updating it to use the new
wording.

Committed to trunk as r255082.

gcc/testsuite/ChangeLog:
	PR tree-optimization/82588
	PR tree-optimization/82583
	* jit.dg/test-error-array-bounds.c (verify_code): Update expected
	error message from -Warray-bounds.
---
 gcc/testsuite/jit.dg/test-error-array-bounds.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/testsuite/jit.dg/test-error-array-bounds.c b/gcc/testsuite/jit.dg/test-error-array-bounds.c
index 732ec87..889c517 100644
--- a/gcc/testsuite/jit.dg/test-error-array-bounds.c
+++ b/gcc/testsuite/jit.dg/test-error-array-bounds.c
@@ -68,5 +68,6 @@ verify_code (gcc_jit_context *ctxt, gcc_jit_result *result)
 
   /* ...and that the message was captured by the API.  */
   CHECK_STRING_VALUE (gcc_jit_context_get_first_error (ctxt),
-		      "array subscript is above array bounds [-Warray-bounds]");
+		      "array subscript 10 is above array bounds of"
+		      " 'unsigned char[10]' [-Warray-bounds]");
 }
-- 
1.8.5.3

                 reply	other threads:[~2017-11-22 21:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1511385398-37122-1-git-send-email-dmalcolm@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jit@gcc.gnu.org \
    --cc=msebor@redhat.com \
    /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: link
Be 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).