From: Nick Clifton <nickc@redhat.com>
To: jitendra@linsyssoft.com
Cc: binutils@sources.redhat.com
Subject: Re: Running gas and ld test suites remotely.
Date: Tue, 01 Feb 2005 10:44:00 -0000 [thread overview]
Message-ID: <41FF5F9C.5040107@redhat.com> (raw)
In-Reply-To: <1107241354.3619.14.camel@ind.linsyssoft.com>
Hi Jitendra,
> I am using powerpc as machine and my host machine is x86.
Have you considered using a powerpc simulator running on the x86 host as
an alternative test environment ? This definitely works.
> I want to use ssh for session
> protocol and scp for transfer protocol. I have successfully run binutils
> test suite remotely but gas and ld test suites runs only on host for the
> similar configurations as binutils.
Do you mean that the GAS executable you have runs on the x86 host and
produces ppc object files, or that it runs on the remote powerpc machine
and produces native object files ? In the former case there really is
no advantage to taking the created object file, downloading it to the
test machine, then uploading it back to the host so that objdump can be
run on it. ie - the GAS testsuite does not check to see if *working*
executables can be created. All it does is check to see if assembler
source files will assemble to certain expected binary patterns. There
is no need for an execution environment for the GAS testsuite - nothing
is ever executed.
Cheers
Nick
next prev parent reply other threads:[~2005-02-01 10:44 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 [this message]
2005-02-02 13:21 ` Jitendra Pawar
2005-02-02 15:40 ` Ramana Radhakrishnan
2005-02-08 15:51 ` Jitendra Pawar
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=41FF5F9C.5040107@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=jitendra@linsyssoft.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).