Using a compiler for testsuite that's not GCC?

Using a compiler for testsuite that's not GCC?

[Timothy Wall]

What's the best way to go about this?  It seems a lot of the tests assume gcc and so throw gcc-specific options at the compiler.  It seems the approach with least effort would be to point dejagnu at a wrapper which translates gcc options into ones the other compiler understands...

T.

Re: Using a compiler for testsuite that's not GCC?

[Andrew Cagney]

> What's the best way to go about this?  It seems a lot of the tests assume gcc and so throw gcc-specific options at the compiler.  It seems the approach with least effort would be to point dejagnu at a wrapper which translates gcc options into ones the other compiler understands...

Can you expand a little.  The testsuite should work with any C compiler.

Andrew

Re: Using a compiler for testsuite that's not GCC?

[Timothy Wall]

Hi Andrew,

I'm talking to a gdbserver which controls my target board.

I'm not yet attuned to the role of each of these configs (could sure use a README in these dirs...), but so far I have the following:

dejagnu/config/tic54x.exp - simply loads gdbserver config
dejagnu/baseboards/tic54x.exp - most config stuff is here, including cflags/ldflags
gdb/testsuite/config/tic54x.exp - loads gdbserver config

Even though I've set cflags, some tests throw in additional options:

Running ../../../gdb/gdb/testsuite/gdb.base/all-bin.exp ...
gdb compile failed, >> WARNING: invalid option -w (ignored)
>> WARNING: invalid option -l (ignored)
>> WARNING: invalid option -m (ignored)
[all-types.c]
[all-types]
Fatal error: could not open source file "/nfs/dev-users/twall/build-gdb/gdb/test
suite/gdb.base/all-types"
1 fatal error detected in the compilation of "/nfs/dev-users/twall/build-gdb/gdb
/testsuite/gdb.base/all-types".
Compilation terminated.
WARNING: Testcase compile failed, so all tests in this file will automatically f
ail.

This looks like "-lm" is tacked on, as well as "-w".  The "-w" in the test is explicit.  I
should be able to override "-lm" if it's in a variable somewhere.




Andrew Cagney wrote:

> > What's the best way to go about this?  It seems a lot of the tests assume gcc and so throw gcc-specific options at the compiler.  It seems the approach with least effort would be to point dejagnu at a wrapper which translates gcc options into ones the other compiler understands...
>
> Can you expand a little.  The testsuite should work with any C compiler.
>
> Andrew

Re: Using a compiler for testsuite that's not GCC?

[Timothy Wall]

Looking at gdb_preprocess and gdb_compile from gdb.exp, it would look like I would need to replace these functions with something that works with my compiler?

Pardon me if I'm being dense, but I'm trying to figure out where are the proper places for configuration mods, and I don't see anything that resembles my configuration.

T.

Andrew Cagney wrote:

> > What's the best way to go about this?  It seems a lot of the tests assume gcc and so throw gcc-specific options at the compiler.  It seems the approach with least effort would be to point dejagnu at a wrapper which translates gcc options into ones the other compiler understands...
>
> Can you expand a little.  The testsuite should work with any C compiler.
>
> Andrew

Re: Using a compiler for testsuite that's not GCC?

[Stan Shebs]

Timothy Wall wrote:
> 
> What's the best way to go about this?  It seems a lot of the tests assume gcc and so throw gcc-specific options at the compiler.  It seems the approach with least effort would be to point dejagnu at a wrapper which translates gcc options into ones the other compiler understands...

Testsuite should be able to work with any compiler, athough in
practice GCCisms sneak in from to time.  Note however that there
is an implicit expectation that the compiler accepts a basic list
of options common to Unix compilers, such as -g, -o, etc.  -l
would be in that category, though not necessarily the list of
libraries, and maybe -w, not sure about that.

If you wanted to generalize the testsuite though, that would be
a good thing.

Stan

Re: Using a compiler for testsuite that's not GCC?

[Timothy Wall]

Well, since my cross compiler uses just about none of the "standard" options, I think I'm going to have to hack away and integrate later...

T.


Stan Shebs wrote:

> Timothy Wall wrote:
> >
> > What's the best way to go about this?  It seems a lot of the tests assume gcc and so throw gcc-specific options at the compiler.  It seems the approach with least effort would be to point dejagnu at a wrapper which translates gcc options into ones the other compiler understands...
>
> Testsuite should be able to work with any compiler, athough in
> practice GCCisms sneak in from to time.  Note however that there
> is an implicit expectation that the compiler accepts a basic list
> of options common to Unix compilers, such as -g, -o, etc.  -l
> would be in that category, though not necessarily the list of
> libraries, and maybe -w, not sure about that.
>
> If you wanted to generalize the testsuite though, that would be
> a good thing.
>
> Stan

Re: Using a compiler for testsuite that's not GCC?

[Timothy Wall]

I think I've found a reasonable solution.

Some things are easy enough to modify (cflags, mathlib), but I ended up having to write my own {target}_compile function which swaps out the unwanted args, replacing them if possible.  I pretty much had to do a rewrite of the default_target_compile function in dejagnu/lib/target.exp since the compiler I'm using has a really heinous command-line configuration that hearkens back to the DOS days.

T.