This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Regarding gcc testsuite
- From: Manpreet Singh <mappysingh at gmail dot com>
- To: gcc-help at gcc dot gnu dot org
- Date: Wed, 29 Oct 2014 10:52:14 +0100
- Subject: Re: Regarding gcc testsuite
- Authentication-results: sourceware.org; auth=none
- References: <CAB6m5eS3eUTUPDPXM-c_+AKNfgfE7yXOmGy--bq_amZnMTJtrQ at mail dot gmail dot com> <CAH6eHdSfF5PPJ8utE8Zek7B+J1qQZDwCpYUJ7JMh7DRuf=HTWQ at mail dot gmail dot com> <CAB6m5eT8mKneAprmiFxNihzRU3wMpxr6+WHnh9BX1LVD5AQkBA at mail dot gmail dot com> <CAH6eHdTC9FjqAqH+5kFpme9Nvs0EG2-AH5A96XVnpWa5Ebzsog at mail dot gmail dot com> <CAB6m5eTzSaEtY2Px__2KuTaprObWRB5GuAn8mdAVSJkQZdsNbA at mail dot gmail dot com> <CAH6eHdQKFzww1SDyWSn8gG7abA-eTs_c2fxLyyUK5LAX7r-bpw at mail dot gmail dot com> <CAB6m5eRUFkEaasKopGoB9JmUAx25CE6GsrP_Lw6neVuqjnUXgg at mail dot gmail dot com> <CAH6eHdTdFGEvgObhiFyvc5A8ngDu+oYSPvk-4puFmu4X6JxomQ at mail dot gmail dot com> <CAB6m5eQ9=5jSDBfZmJVsw+TgRvZzti3LAwA5YpFCcrRnSs+spw at mail dot gmail dot com>
Hi,
According to my last mail. Is there any way to figure out the issue?
Thanks & regards
mappy
On 10/28/14, Manpreet Singh <mappysingh@gmail.com> wrote:
> Hi,
> You are right its 32-bit assembler. I tried these 2 ways to configure
>
> Way 1
> My configuration:-
> In my pc latest version of gcc-4.8 is install and i want to configure
> and run gcc testsuite for gcc-4.4.5
> Ubuntu 14.04
> Host = x86_64-linux-gnu
> Build = x86_64-linux-gnu
> Target = powerpc-linux-gnu
>
> These are the steps which i performed to run testsuite
> I am trying to run configure with this script
>
> a) sourcedir.../gcc-4.4.5/configure --prefix=/tmp/gcc-4.4.5
> --enable-languages=c,c++ --build=x86_64-pc-linux-gnu
> --host=x86_64-pc-linux-gnu --target=powerpc-linux-gnu
> --enable-languages=c,c++ --enable-long-long
>
>
> b) And then to build gcc :-
> make all-gcc
>
> c) To run the testsuite :- builddir.../gcc-4.4.5/gcc
> make check (in build dir)
>
> This is the failure when i configured gcc-4.4.5 with above script
> Failure is
> FAIL: gcc.c-torture/compile/20000105-1.c -O0 (test for excess errors)
> Excess errors:
> /build_dir.../gcc-4.4/new_build/gcc/as: 76: exec: : Permission denied
> same failure many thousand times.
>
> _________________________________________________________________________________________________________________________________________________________________________________________________________
>
> Way 2
>
> a) I used already built assembler i.e. i already mentioned above is
> 32 bit assembler
> sourcedir.../gcc-4.4.5/configure --prefix=/tmp/gcc-4.4.5
> --with-as=/path/to/..../bin/ppc_oea-as
> --with-ld=/path/to/..../bin/ppc_oea-ld --enable-languages=c,c++
> --disable-bootstrap --disable-libgomp --disable-libstdcxx-pch
> --with-ranlib=/path/to/..../bin/ppc_oea-ranlib
>
>
> b) And then to build gcc :-
> make all-gcc
>
> c) To run the testsuite :- builddir.../gcc-4.4.5/gcc
> make check(in build dir)
>
>
> And this the failure when i configured with way 2
>
> /tmp/cc7EMVR7.s: Assembler messages:
> /tmp/cc7EMVR7.s:8: Error: Unrecognized opcode: `pushq'
> /tmp/cc7EMVR7.s:10: Error: Unrecognized opcode: `movq'
> /tmp/cc7EMVR7.s:13: Error: Unrecognized opcode: `subq'
> same failure many thousand times.
>
> Thanks & regards
> Manpreet Singh
>
> On 10/28/14, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>> On 28 October 2014 10:33, Manpreet Singh wrote:
>>> Hi,
>>> Thanks, now i can build it without error. But, when i run that
>>> make check(testsuite) in command line.
>>> Again giving lots of failure.
>>> e.g
>>> /tmp/cc7EMVR7.s: Assembler messages:
>>> /tmp/cc7EMVR7.s:8: Error: Unrecognized opcode: `pushq'
>>> /tmp/cc7EMVR7.s:10: Error: Unrecognized opcode: `movq'
>>> /tmp/cc7EMVR7.s:13: Error: Unrecognized opcode: `subq'
>>> same failure many thousand times.
>>> How would i get rid off this failure?
>>
>> Your assembler doesn't understand x86_64 instructions. I would guess
>> either you've got a 32-bit x86 assembler or an assembler for a totally
>> different architecture.
>>
>> It would probably help if you said what kind of system you're running
>> on and how you configured GCC, so we don't have to guess what you're
>> trying to do.
>>
>