9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mike Haertel <9fans@ducky.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sleep-complexity
Date: Mon,  9 May 2005 09:45:44 -0700	[thread overview]
Message-ID: <200505091645.j49Gji1d001933@ducky.net> (raw)
In-Reply-To: <bb859ceba1e1137d3efd3b788a9c0979@collyer.net>

>> All the world is no longer a 32-bit 386.
>
>True, but the pain of the PDP-11-to-VAX migration, when `int' changed
>from 16 bits to 32, seems to have convinced the standards
>organisations that they don't want to change the sizes of any integral
>types.  The proposed sizes for 64-bit implementations (in `LLP64')
>are: 32 bits for int and long, 64 for long long and pointers.  And
>ANSI & POSIX will continue to paper over size differences with *_t
>types.
>
>I'd prefer 64-bit longs and no long longs (or 128-bit long longs), but
>that seems unlikely given the vast existing corpus of code written
>without much attention to types.

Wow, you're a little out of date.

The *BSDs and Linux did the Right Thing: on Alpha and AMD64
(the two flavors of which I have personal knowledge) "long"
is 64 bits.

So the vast corpus of software that has been ported to
64-bit *BSD and Linux systems is now free of the assumption
that sizeof (int) == sizeof (long).

There is still a pervasive assumption that ints are 32 bits.


  parent reply	other threads:[~2005-05-09 16:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-08 12:03 Christoph Lohmann
2005-05-08 12:51 ` Sergey Reva
2005-05-08 16:50   ` Russ Cox
2005-05-08 17:28     ` Dan Cross
2005-05-08 18:56       ` jmk
2005-05-08 19:21         ` Bruce Ellis
2005-05-08 20:54           ` Charles Forsyth
2005-05-08 21:06             ` Charles Forsyth
2005-05-08 22:40         ` Dan Cross
2005-05-08 22:59           ` geoff
2005-05-09  7:28             ` Richard Miller
2005-05-09 13:14             ` Brantley Coile
2005-05-09 16:45             ` Mike Haertel [this message]
2005-05-09 20:10               ` Bruce Ellis
2005-05-09 22:46                 ` Charles Forsyth
2005-05-09  7:41           ` David Tolpin
2005-05-08 21:12       ` Charles Forsyth
2005-05-09 13:29         ` Nigel Roles
2005-05-09 14:03           ` Charles Forsyth
2005-05-10 17:09         ` boyd, rounin
2005-05-10 17:15           ` jmk
2005-05-10 18:34             ` boyd, rounin
2005-05-10 18:39               ` rog
2005-05-10 19:27               ` Ronald G. Minnich
2005-05-10 21:02                 ` David Leimbach
2005-05-10 21:20                   ` Bruce Ellis

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=200505091645.j49Gji1d001933@ducky.net \
    --to=9fans@ducky.net \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).