[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [DejaGnu] How to test an executable which comprises few object files
Re: [DejaGnu] How to test an executable which comprises few object files?
Mon, 17 Sep 2001 18:00:12 -0600
On Mon, Sep 17, 2001 at 04:51:23PM -0700, Nitin Gupta wrote:
> please excuse me for not being clear. What I meant was that there are few
> source files, those need to be compiled and linked into a executable. Where
> can I keep those source files in current testsuite structure? and How should I
> mention the object file dependancies? If I can mention it in target specific
You copy the source code to the gcc/testsuite/gcc.c-torture/execute
subdirectory, and they're automatically added. The only restriction is
that each test case must be contained in one source file. If your test case
refers to other object files for compilation, then it shouldn't be part of
the GCC Torture test, it needs to be in it's own test suite directory. Then
you can get full control of compilation and linking.
When I wrote the wrappers for GCC to use Tege's C Torture test, it was
setup to only run those existing tests, in his existing style. It's a bit
limited, but worked well so I could use his test cases for GCC testing.
- rob -