selective set of tests in gcc-4.5.1 test suite Post: 302468846

Sponsored Content

Top Forums UNIX for Advanced & Expert Users selective set of tests in gcc-4.5.1 test suite Post 302468846 by ganesh2282 on Thursday 4th of November 2010 02:37:48 AM

11-04-2010

Registered User

selective set of tests in gcc-4.5.1 test suite

Hi,

I am unable to run a selective set of tests in gcc-4.5.1 test suite.
I tried two runtest commands given below (output is also given below).
Can you please guide me how to run specific set of tests for example :
I would like to run only tests gcc.target/i386/avx-vaddpd-1.c and gcc.target/i386/avx-vaddpd-256-1.c ?

Command-1:This command runs 10 tests but does not run one the i mentioned gcc.target/i386/avx-vaddpd-1.c

Code:

$ cd gcc/testsuite 
$ runtest -tool_exec gcc --src-dir=. --tool gcc  i386.exp=gcc.target/i386/avx-vaddpd-1.c

Output:
WARNING: Couldn't find the global config file.
Test Run By root on Tue Jan 25 21:05:23 2011
Native configuration is x86_64-unknown-linux-gnu

=== gcc tests ===

Schedule of variations:
unix

Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/default.exp as tool-and-target-specific interface file.
Running ./gcc.target/i386/i386.exp ...

=== gcc Summary ===

# of expected passes 10
/home/ganesh/gcc_test-suite/install_4_5_1/bin/gcc version 4.5.1 (GCC)

Command-2:This command runs all tests under i386 folder

Code:

$ runtest -tool_exec gcc --src-dir=gcc/testsuite --tool gcc  gcc.target/i386/i386.exp=gcc.target/i386/avx-vaddpd-1.c

Notes:
gcc version 4.5.1
GNU assembler version 2.20.1
OS: SLES10-SP1
-Thanks and regards,
Ganesh

Last edited by vbe; 11-04-2010 at 06:46 AM.. Reason: code tags pleae

ganesh2282

View Public Profile for ganesh2282

Find all posts by ganesh2282

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

test-and-set in bash

I'm not talking about the assembly instruction TAS, a better name could be check-and-set :) Anyway, is there a way to simplify the following if ; then VAR="something"; fi I have ~20 variables that should be test-and-set like this, and it really looks lame.

2. Solaris

Installing gcc - recieve error message gcc : cannot execute

AIM- Install Oracle 11g on Solaris using VMWare Steps 1.Logged on as root 2.Created subfolders � /usr/local/bin & /usr/local/bin/gcc 3.Downloaded gcc & libiconv & unzipped them on my harddrive & burnt them on CD 4.Copied files from CD to /usr/local/bin/gcc 5.Terminal (root) � pkgadd -d...

3. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the...

4. Shell Programming and Scripting

How to check weather a string is like test* or test* ot test in if condition

How to check weather a string is like test* or test* ot *test* in if condition

LEARN ABOUT DEBIAN

runtest

runtest(1)						      General Commands Manual							runtest(1)

NAME

       runtest - DejaGnu test driver

SYNOPSIS

       runtest [OPTION]...

DESCRIPTION

       DejaGnu	is  a  framework for testing programs using Expect.  runtest is the driver program for DejaGnu.  It controls what tests to run and
       how to run them.

OPTIONS

       --all  Output all test results. By default, only unexpected results are displayed.

       --debug
	      Turn on expect internal debugging output. The output is logged to a file called dbg.out.

       --build TRIPLET
	      The configuration TRIPLET for the build system.

       --directory DIRECTORY
	      Run only tests in the specified DIRECTORY.

       --help Prints out a help screen and then exits.

       --host TRIPLET
	      The configuration TRIPLET for the host system.

       --host_board NAME
	      The host board defintion to use.

       --ignore test1.exp test2.exp ...
	      Do not run the specified tests.

       --mail 'name1 name2 ...'
	      Electronic mail addresses to receive test results.

       --name HOSTNAME
	      The network HOSTNAME of the target board.

       --objdir PATH
	      PATH is a directory containing compiled test code.

       --outdir DIRECTORY
	      The name of a DIRECTORY for test log output.

       --reboot
	      Reboot the target board when runtest initializes (if supported).

       --srcdir PATH
	      PATH is a directory containing test directories.

       --status
	      Set the exit status to fail on Tcl errors.

       --strace N
	      Turns on expect internal tracing to N levels deep. The output is logged to a file called dbg.out.

       --target TRIPLET
	      The configuration TRIPLET for the target.

       --target_board NAME
	      A list of target board NAMEs to run tests on.

       --tool TOOLNAME
	      Specify the tool to be tested.  TOOLNAME controls the test suite applied, and the associated initialization module.

       --tool_exec PATH
	      Specify the PATH to the executable to test.

       --tool_opts OPTIONS
	      Additional OPTIONS to pass to the tool.

       --verbose, -v
	      Turns on more debugging output from test cases and DejaGnu utility code.	Use more than once to increase output further.

       --version, -V
	      Prints out the versions of DejaGnu, Expect and Tcl.

       --xml, -x
	      Generate XML output.

       -D[number]
	      Activate the Tcl debugger.  number can be either 1 or 0. If it is 1, then the expect shell will break when it  starts  to  run.  The
	      interrupt key will cause DejaGnu to drop to the debugger prompt. If it is 0, DejaGnu starts as usual, but a ^C drops to the debugger
	      prompt.

       Any file name on the command line is assumed to be a subset of the
       test names to run.  Usually these are the names of the test scripts (eg. foo.exp).

       Makefile-style variables are used to specify tool names and their flags; these and other configuration dependent values are  saved  in  the
       file site.exp, created during configuration.

EXIT CODES

       runtest sets the exit code to 1 if any of the tests failed, or sets it to 0 if all the tests passed.

AUTHOR

       Rob Savoye (rob@welcomehome.org)

REPORTING BUGS

       Report bugs to <bug-dejagnu@gnu.org>.

COPYRIGHT

       Copyright (C) 2005, 2007, 2008 Free Software Foundation, Inc.
       This   is   free   software.    You   may   redistribute   copies   of	it   under   the   terms   of	the  GNU  General  Public  License
       <http://www.gnu.org/licenses/gpl.html>.	There is NO WARRANTY, to the extent permitted by law.

SEE ALSO

       The full documentation for DejaGnu is maintained as a Docbook manual.  If the info program is properly installed at your site, the command

	      info dejagnu

       should give you access to the complete manual.

								    2008-02-25								runtest(1)