On Fri, Jan 17, 2020 at 03:11:40PM +0100, Jakub Jelinek wrote:
> On Fri, Jan 17, 2020 at 09:07:01AM -0500, Jason Merrill wrote:
> > On 12/30/19 3:51 PM, Kerem Kat wrote:
> > > +/* { dg-message "expected" "expected" { target *-*-* } .3 } */
> >
> > Dejagnu doesn't like this:
> >
> > ERROR: c-c++-common/pr92833-4.c -std=c++98: expected integer but got ".3"
> > for " dg-message 4 "expected" "expected" { target *-*-* } .3 "
>
> Yeah, it can handle .-3 if you want 3 lines before the one with dg-message,
> or .+3 if you want 3 lines after it, or . for current line (then you can
> leave that and target out), or exact line number, or some symbolic name if
> earlier marked.
Fixed thusly, committed as obvious to trunk.
2020-01-18 Jakub Jelinek <ja...@redhat.com>
PR c/92833
* c-c++-common/pr92833-4.c: Fix dg-message syntax.
--- gcc/testsuite/c-c++-common/pr92833-4.c.jj 2020-01-17 09:31:28.672194093
+0100
+++ gcc/testsuite/c-c++-common/pr92833-4.c 2020-01-18 13:51:33.718394204
+0100
@@ -1,7 +1,7 @@
/* Six marker characters at EOF, causes conflict marker detector to peek 4
tokens. */
-/* { dg-message "expected" "expected" { target *-*-* } .3 } */
+/* { dg-message "expected" "expected" { target *-*-* } .+1 } */
>>
>>
>>
\ No newline at end of file
Jakub
