From: Jitendra Pawar <jitendra@linsyssoft.com>
To: ramana.radhakrishnan@codito.com
Cc: Nick Clifton <nickc@redhat.com>, binutils@sources.redhat.com
Subject: Re: Running gas and ld test suites remotely.
Date: Tue, 08 Feb 2005 15:51:00 -0000 [thread overview]
Message-ID: <1107849045.3620.24.camel@ind.linsyssoft.com> (raw)
In-Reply-To: <33171.203.212.198.107.1107358264.squirrel@webmail.codito.com>
> Ok, generally the GAS testsuite works as follows :
>
> We specify the assembly files and the equivalent disassembly files.
> Remember GAS only produces object modules and not executables. So the way
> one specifies a testcase is to provide a .s and a .d file which are
> essentially the source assembler file and the expected disassembly file.
> So the testsuite runs the assembler , does an objdump using the objdump
> from the build tree and compares the output of the two.
>
> As Nick said in an earlier post, there is really no need to execute the
> executables.
>
>
>
> > Is there any document that describes functionality of gas test suite?
> > Does ld test suite have same nature(nothing is ever executed.) as gas?
>
> Again the linker testsuite is similar. The linker in addition to creating
> executables fundamentally creates a memory layout for the executable,
> hence it is enough to check if the sections have been laid out as
> expected. So AFAIK there is no actual executable that gets run by the
> linker.
>
> Also with the linker its enough to test for the same. You do a ld -r and
> check that the relocs produced are as expected / the section headers
> produced are as expected etc. etc.
>
Hi Ramana and Nick,
Thank you for your help.
I would also like to know how to run a single file from gas test suite?
I am able to run gas test suite in a one shot and got 72 PASSES without
any error or failure. But when I am trying to run a single file (e.g.
gas/cfi/cfi.exp) as:
$runtest gas/cfi/cfi.exp
then I got an error generated in dejagnu (runtest.exp file).
----------------------------------
send: spawn id exp0 not open
while executing
"send_user "$message\n""
("default" arm line 2)
invoked from within
"case "$firstword" in {
{"PASS:" "XFAIL:" "KFAIL:" "UNRESOLVED:" "UNSUPPORTED:"
"UNTESTED:"} {
if $all_flag {
send_user "$message\n"
return "..."
(procedure "clone_output" line 10)
invoked from within
"clone_output "\n\t\t=== $tool Summary ===\n""
(procedure "log_summary" line 23)
invoked from within
"log_summary total"
(procedure "log_and_exit" line 5)
invoked from within
"log_and_exit"
(file "/usr/local/share/dejagnu/runtest.exp" line 1912)
-------------------------------
Does gas test suite support for execution of single .exp file??
thanks
Jitendra
> HTH
> cheers
> Ramana
>
> ----
> Ramana Radhakrishnan
> GNU Tools
> (codito ergo sum) www.codito.com
>
>
next prev parent reply other threads:[~2005-02-08 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 7:12 Jitendra Pawar
2005-02-01 7:21 ` Jitendra Pawar
2005-02-01 10:44 ` Nick Clifton
2005-02-02 13:21 ` Jitendra Pawar
2005-02-02 15:40 ` Ramana Radhakrishnan
2005-02-08 15:51 ` Jitendra Pawar [this message]
2005-02-08 16:01 ` Nick Clifton
2005-02-08 17:31 ` Running Individual tests from gas suites Jitendra Pawar
2005-02-08 20:19 ` Hans-Peter Nilsson
2005-02-09 10:12 ` Jitendra Pawar
2005-02-09 16:58 ` Nick Clifton
2005-02-10 13:13 ` Jitendra Pawar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1107849045.3620.24.camel@ind.linsyssoft.com \
--to=jitendra@linsyssoft.com \
--cc=binutils@sources.redhat.com \
--cc=nickc@redhat.com \
--cc=ramana.radhakrishnan@codito.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).