On 06/29/2018 08:04 PM, David Malcolm wrote:
On Fri, 2018-06-29 at 13:19 -0400, Eric Gallager wrote:
On 6/29/18, Martin Liška wrote:
Hi.
I would like to add some DejaGNU tests for completion option.
Ready for trunk?
Martin
Presumably the point of the DejaGnu tests is:
(a) to give us some i
On Fri, 2018-06-29 at 13:19 -0400, Eric Gallager wrote:
> On 6/29/18, Martin Liška wrote:
> > Hi.
> >
> > I would like to add some DejaGNU tests for completion option.
> >
> > Ready for trunk?
> > Martin
Presumably the point of the DejaGnu tests is:
(a) to give us some integration testing, to c
On 6/29/18, Martin Liška wrote:
> Hi.
>
> I would like to add some DejaGNU tests for completion option.
>
> Ready for trunk?
> Martin
>
So, correct me if I'm wrong, but these tests would need to be updated
every time a new option starting like one of those is added, right? If
so, can you think of
Sep 17 00:00:00 2001
> From: marxin
> Date: Fri, 29 Jun 2018 11:18:21 +0200
> Subject: [PATCH] Add new tests for --completion option.
>
> gcc/testsuite/ChangeLog:
>
> 2018-06-29 Martin Liska
>
> * gcc.dg/completion-1.c: New test.
> * gcc.dg/completion-2.c: New test.
> * gcc.dg/completion-3.c: New test.
OK
jeff
Hi.
I would like to add some DejaGNU tests for completion option.
Ready for trunk?
Martin
>From a735068032aa9ce82e5f56172f1b99bc2c90ac0f Mon Sep 17 00:00:00 2001
From: marxin
Date: Fri, 29 Jun 2018 11:18:21 +0200
Subject: [PATCH] Add new tests for --completion option.
gcc/testsuite/Change
