Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "J. Scott Kasten" <jsk@tetracon-eng.net>
Cc: Brandon Barker <bebarker@meginc.com>,
	"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Indy 64 or 32 bit?
Date: Wed, 8 Aug 2001 17:18:06 +0200	[thread overview]
Message-ID: <20010808171806.A4105@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.SGI.4.33.0108081042090.23638-100000@thor.tetracon-eng.net>; from jsk@tetracon-eng.net on Wed, Aug 08, 2001 at 11:02:44AM -0400

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
> 
> Run:
> 
>   sizeof(int) = 8, sizeof(*) = 8
>   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
>         <snip>
>         daddu $3,$2,1
> 
> Does N32 legitimately allow 64 bit instructions,

Yes.  Hey, that's the 80% of the purpose of N32!

> 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.  If you really want to read about N32 get the
respective docs from techpubs.sgi.com.

  Ralf

  reply	other threads:[~2001-08-08 15:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07  3:47 Indy 64 or 32 bit? Brandon Barker
2001-08-07  3:56 ` George Gensure
2001-08-07  4:03   ` nick
2001-08-07  4:11     ` Nils C. Anderson
2001-08-07  4:11       ` Nils C. Anderson
2001-08-07 14:42 ` Ralf Baechle
2001-08-08  0:45 ` J. Scott Kasten
2001-08-08 10:17   ` Ralf Baechle
2001-08-08 15:02     ` J. Scott Kasten
2001-08-08 15:18       ` Ralf Baechle [this message]
2001-08-08 15:41         ` Thiemo Seufer
2001-08-08 20:12           ` J. Scott Kasten
2001-08-08 21:16             ` Thiemo Seufer
2001-08-09 12:08             ` Ralf Baechle

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=20010808171806.A4105@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=bebarker@meginc.com \
    --cc=jsk@tetracon-eng.net \
    --cc=linux-mips@oss.sgi.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox