This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: testsuite execution question


On Mon, Feb 28, 2005 at 04:14:12PM -0800, Janis Johnson wrote:
> > DejaGnu's definition of ${tool}_load has an optional argument for flags
> > to pass to the test program, but none of the procedures in DejaGnu or in
> > gcc/testsuite/* are set up to pass such flags.  It would be fairly
> > straightforward to provide a local version of gfortran_load to intercept
> > calls to the global one, and have it add flags specified with a new test
> > directive to the DejaGnu version of ${tool}_load.  That directive could
> > be something like:
> > 
> >   { dg-program-options options [{ target selector }] }
> > 
> > Would something like this be useful for other languages as well, or is
> > Fortran the only one in GCC that has support to process a program's
> > command line?
> > 
> > I'm willing to implement something like this if it looks worthwhile.
> 
> It's supposed to be possible to drop in replacements to DejaGnu in the
> GCC testsuite; do other test frameworks of interest handle passing
> arguments to the test program in a way that could support this?  (Sorry
> for talking to myself here.)

I don't think that's the concern here - it's more a matter of whether
the target, and DejaGNU, support this.  Lots of embedded targets seem
to have trouble with it.  Take a look at "noargs" in the DejaGNU board
files for a couple of examples, IIRC.  GDB jumps through some hoops to
test this, and gets it wrong in a bunch of places too.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]