linux-mips
[Top] [All Lists]

Re: Indy 64 or 32 bit?

To: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Indy 64 or 32 bit?
From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Date: Wed, 8 Aug 2001 17:41:42 +0200
In-reply-to: <20010808171806.A4105@bacchus.dhis.org>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.3.18i
Ralf Baechle wrote:
> On Wed, Aug 08, 2001 at 11:02:44AM -0400, J. Scott Kasten wrote:
> 
> >    gcc -mips3 -mint64 test.c -o test
> > 
> > The file command says:
> > 
> >   test:           ELF N32 MSB mips-3 dynamic executable (not stripped) MIPS 
> > - version 1
                          ^^^
I don't know how file detects this, but at least current CVS gas
does not set the appropriate flag in the object file header.

> > 
> > Run:
> > 
> >   sizeof(int) = 8, sizeof(*) = 8
                    ^              ^
This should be both 4, I assume this happened due to -mint64.

> >   Result: 11
> > 
> > If we look at the assembly, we see a sign extended 64 bit load, and a 64
> > bit add.  So we are indeed generating 64 bit instructions, at least in
> > some cases.
> > 
> >         dli $3,0xa # 10

To what does this dli get expanded? I'm interested in the output of
objdump -d.

[snip]
> > or is this an example of code that I've truely "munged" togeather?
> 
> Doubleplusyesyesyes :-)  -mint64 is not valid for any MIPS code model.  Gas
> is royally b0rken for N32.

WRT what?


Thiemo

<Prev in Thread] Current Thread [Next in Thread>