linux-mips
[Top] [All Lists]

Re: mips linux glibc-2.3.3 build - opcode not supported problem

To: linux-mips@linux-mips.org
Subject: Re: mips linux glibc-2.3.3 build - opcode not supported problem
From: "T. P. Saravanan" <sara@procsys.com>
Date: Mon, 04 Oct 2004 10:49:03 +0530
In-reply-to: <026b01c4a6d5$179b11e0$1701a8c0@vmbservice.ru>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <026b01c4a6d5$179b11e0$1701a8c0@vmbservice.ru>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla Thunderbird 0.7.2 (Windows/20040707)
Hi,

okay.  Now I have put my CFLAGS to
export CFLAGS="-mips32 -O2 -g"

This too takes me beyond "opcode not supported on this processor" error.

But, the build is breaking at a later point - it is something to do with
#defines like _MIPS_SIM _ABIN32 _ABI64 etc.  Anyway, I will post the
problem in an independent mail.

Thanks,
Saravanan.

Alec Voropay wrote:

Hi!

The original   mips1 (32-bit R3000) has no sc/ll instructions.

This sc/ll instructions are from the mips3 (64-bit R4000) command set.

It seems, you should use newest "hybrid"  mips32 (designed for the SOC)
:
the ISA-II+  architecture but 32bit + *extended instrution set* .

--
-=AV=-


-----Original Message-----
From: linux-mips-bounce@linux-mips.org [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of T. P. Saravanan
Sent: Thursday, September 30, 2004 9:43 AM
To: linux-mips@linux-mips.org
Subject: mips linux glibc-2.3.3 build - opcode not supported problem


[-snip-]

The problem seems to go away if I put CFLAGS="-mips4 -O2 -g". Is it OK to do this?
Why did gcc/gas fail to use -mips4 opcodes by default?

-Saravanan






<Prev in Thread] Current Thread [Next in Thread>
  • Re: mips linux glibc-2.3.3 build - opcode not supported problem, T. P. Saravanan <=