Re: How do I add target specific tests?

1 msg	[tuples] Merged with trunk @135126
4 msg	IRA performance testing on Fortran
14 msg	bit_size_type - a data type?
1 msg	About symbol and label
2 msg	[Windows] Fixing fprintf errors breaking bootst...
3 msg	inline assembly question (memory side-effects)

How do I add target specific tests?
\ Andy H (10 May 2008)
. \ Alexandre Oliva (10 May 2008)
. . \ Daniel Jacobowitz (12 May 2008)

2 msg	Deprecation?!
1 msg	gcc-4.4-20080509 is now available
1 msg	RFC: Optimize caller-saved register
6 msg	How to handle loop iterator variable?
7 msg	Division using FMAC, reciprocal estimates and N...
1 msg	Questions about attributes
2 msg	ssa_name issues
6 msg	RFH: Building and testing gimple-tuples-branch
1 msg	gcc-4.3-20080508 is now available
4 msg	How to implement the instruction in the back end
1 msg	gcc-4.2-20080507 is now available
5 msg	all-target-libstdc++-v3 broken again
22 msg	Bad code generation on HPPA platform

Subject:	Re: How do I add target specific tests?
Group:	Gcc
From:	Daniel Jacobowitz
Date:	12 May 2008

On Sat, May 10, 2008 at 04:09:03PM -0300, Alexandre Oliva wrote:
> On May 10, 2008, Andy H <hutchinsonandy> wrote:
>
> > These would be testcases for PR that fail related to AVR back end
> > problems - rather than testcases for generic PR.
>
> > Do I just add them to directory testsuite/gcc.target/avr? Or are there
> > some other configuration steps needed?
>
> You'll want to create a .exp file that exists right away if the target
> is not what you want, and that runs the testing machinery otherwise.
> Look for `istarget' in testsuite/gcc.target/*/*.exp for various
> examples.

But if they expose AVR backend problems, rather than only making sense
on AVR, you can just put them in gcc.c-torture or gcc.dg. Tests for
target-specific features should go in gcc.target but tests for
target-specific bugs may show up bugs on other targets, so it's better
to run them everywhere.

--
Daniel Jacobowitz
CodeSourcery