From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20925 invoked by alias); 2 Feb 2005 15:40:23 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 20861 invoked from network); 2 Feb 2005 15:40:13 -0000 Received: from unknown (HELO marvin.codito.net) (203.197.88.2) by sourceware.org with SMTP; 2 Feb 2005 15:40:13 -0000 Received: from webmail.codito.com (localhost [127.0.0.1]) by marvin.codito.net (8.13.3/8.13.3/Debian-3) with ESMTP id j12FV2st012842; Wed, 2 Feb 2005 21:01:03 +0530 Received: from 203.212.198.107 (SquirrelMail authenticated user ramana.radhakrishnan) by webmail.codito.com with HTTP; Wed, 2 Feb 2005 21:01:04 +0530 (IST) Message-ID: <33171.203.212.198.107.1107358264.squirrel@webmail.codito.com> In-Reply-To: <1107349858.3622.31.camel@ind.linsyssoft.com> References: <1107241354.3619.14.camel@ind.linsyssoft.com> <41FF5F9C.5040107@redhat.com> <1107349858.3622.31.camel@ind.linsyssoft.com> Date: Wed, 02 Feb 2005 15:40:00 -0000 Subject: Re: Running gas and ld test suites remotely. From: "Ramana Radhakrishnan" To: jitendra@linsyssoft.com Cc: "Nick Clifton" , binutils@sources.redhat.com Reply-To: ramana.radhakrishnan@codito.com User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Status: Clean X-SW-Source: 2005-02/txt/msg00055.txt.bz2 Hi Jitendra, > I think I am lacking in understanding functionality of gas test suite. 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. HTH cheers Ramana ---- Ramana Radhakrishnan GNU Tools (codito ergo sum) www.codito.com