From: "Kevin D. Kissell" <kevink@mips.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
"Tor Arntsen" <tor@spacetec.no>
Cc: "Carsten Langgaard" <carstenl@mips.com>,
"Ralf Baechle" <ralf@linux-mips.org>, <linux-mips@linux-mips.org>
Subject: Re: 64-bit and N32 kernel interfaces
Date: Thu, 5 Sep 2002 14:48:15 +0200 [thread overview]
Message-ID: <010301c254da$892fcc50$10eca8c0@grendel> (raw)
In-Reply-To: Pine.GSO.3.96.1020905134606.2423G-100000@delta.ds2.pg.gda.pl
From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
>
> On Thu, 5 Sep 2002, Tor Arntsen wrote:
>
> > > Any reference? AFAIK, long is 64-bit for n32 and only void * is 32-bit.
> > >It doesn't make sense otherwise.
> >
> > On SGI/Irix n32 long and void* are 32-bit, only long long is 64-bit.
> > On SGI/Irix n64 long and void* are 64-bit too.
>
> Hmm, it looks pretty much broken if that's true (especially given long
> long was non-standard untile very recently). I'll check the docs, yet.
n32 has the same data types as o32, an "ILP32" C integer
model. n64 is a pretty normal "LP64" C integer model.
What do you consider to be broken, and how would you
have preferred it to have been done?
Regards,
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, Tor Arntsen <tor@spacetec.no>
Cc: Carsten Langgaard <carstenl@mips.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: 64-bit and N32 kernel interfaces
Date: Thu, 5 Sep 2002 14:48:15 +0200 [thread overview]
Message-ID: <010301c254da$892fcc50$10eca8c0@grendel> (raw)
Message-ID: <20020905124815.50nW4DXyc_5a3a8M3e9d-dAvCksAB8PYDLfFPptcRUw@z> (raw)
In-Reply-To: Pine.GSO.3.96.1020905134606.2423G-100000@delta.ds2.pg.gda.pl
From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
>
> On Thu, 5 Sep 2002, Tor Arntsen wrote:
>
> > > Any reference? AFAIK, long is 64-bit for n32 and only void * is 32-bit.
> > >It doesn't make sense otherwise.
> >
> > On SGI/Irix n32 long and void* are 32-bit, only long long is 64-bit.
> > On SGI/Irix n64 long and void* are 64-bit too.
>
> Hmm, it looks pretty much broken if that's true (especially given long
> long was non-standard untile very recently). I'll check the docs, yet.
n32 has the same data types as o32, an "ILP32" C integer
model. n64 is a pretty normal "LP64" C integer model.
What do you consider to be broken, and how would you
have preferred it to have been done?
Regards,
Kevin K.
next prev parent reply other threads:[~2002-09-05 12:47 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 9:30 64-bit and N32 kernel interfaces Tor Arntsen
2002-09-05 11:47 ` Maciej W. Rozycki
2002-09-05 12:48 ` Kevin D. Kissell [this message]
2002-09-05 12:48 ` Kevin D. Kissell
2002-09-05 14:09 ` Maciej W. Rozycki
2002-09-05 14:20 ` Hartvig Ekner
2002-09-05 14:20 ` Hartvig Ekner
2002-09-05 14:54 ` Maciej W. Rozycki
2002-09-05 14:59 ` Daniel Jacobowitz
2002-09-05 15:10 ` Maciej W. Rozycki
2002-09-05 15:14 ` Daniel Jacobowitz
2002-09-05 16:16 ` Maciej W. Rozycki
2002-09-05 16:19 ` Daniel Jacobowitz
2002-09-05 16:33 ` Maciej W. Rozycki
2002-09-05 16:39 ` Daniel Jacobowitz
2002-09-05 17:16 ` Maciej W. Rozycki
2002-09-05 17:29 ` Kevin D. Kissell
2002-09-05 17:29 ` Kevin D. Kissell
2002-09-05 19:34 ` Maciej W. Rozycki
2002-09-06 9:42 ` Ralf Baechle
2002-09-05 18:07 ` Hartvig Ekner
2002-09-05 18:07 ` Hartvig Ekner
2002-09-05 18:54 ` Maciej W. Rozycki
2002-09-05 19:16 ` Thiemo Seufer
2002-09-06 9:30 ` Ralf Baechle
2002-09-05 14:22 ` Daniel Jacobowitz
2002-09-05 15:08 ` Maciej W. Rozycki
2002-09-05 15:14 ` Daniel Jacobowitz
2002-09-05 16:28 ` Maciej W. Rozycki
2002-09-05 16:30 ` Thiemo Seufer
2002-09-05 16:54 ` Maciej W. Rozycki
2002-09-05 17:44 ` Thiemo Seufer
2002-09-05 19:50 ` Maciej W. Rozycki
2002-09-05 22:12 ` Thiemo Seufer
2002-09-09 17:39 ` Maciej W. Rozycki
2002-09-06 10:14 ` Ralf Baechle
2002-09-09 14:01 ` Dominic Sweetman
-- strict thread matches above, loose matches on Subject: below --
2002-09-04 13:56 Ralf Baechle
2002-09-04 14:14 ` Maciej W. Rozycki
2002-09-04 14:31 ` Ralf Baechle
2002-09-04 15:19 ` Maciej W. Rozycki
2002-09-04 18:46 ` Ralf Baechle
2002-09-05 9:53 ` Maciej W. Rozycki
2002-09-05 6:40 ` Carsten Langgaard
2002-09-05 9:23 ` Maciej W. Rozycki
2002-09-05 13:41 ` Daniel Jacobowitz
2002-09-04 17:32 ` Jun Sun
2002-09-04 17:56 ` Maciej W. Rozycki
2002-09-04 18:40 ` Ralf Baechle
2002-09-05 10:15 ` Kjeld Borch Egevang
2002-09-05 10:15 ` Kjeld Borch Egevang
2002-09-09 20:20 ` Jay Carlson
2002-09-16 13:01 ` Ralf Baechle
2002-09-16 15:40 ` 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='010301c254da$892fcc50$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=carstenl@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@linux-mips.org \
--cc=tor@spacetec.no \
/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