All of lore.kernel.org
 help / color / mirror / Atom feed
From: "T. P. Saravanan" <sara@procsys.com>
To: linux-mips@linux-mips.org
Subject: Re: mips linux glibc-2.3.3 build - opcode not supported problem
Date: Mon, 04 Oct 2004 10:49:03 +0530	[thread overview]
Message-ID: <4160DD47.5010005@procsys.com> (raw)
In-Reply-To: <026b01c4a6d5$179b11e0$1701a8c0@vmbservice.ru>

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
>>
>>
>>
>>
>>    
>>

       reply	other threads:[~2004-10-04  5:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <026b01c4a6d5$179b11e0$1701a8c0@vmbservice.ru>
2004-10-04  5:19 ` T. P. Saravanan [this message]
2004-09-30  5:42 mips linux glibc-2.3.3 build - opcode not supported problem T. P. Saravanan

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=4160DD47.5010005@procsys.com \
    --to=sara@procsys.com \
    --cc=linux-mips@linux-mips.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.