All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] What's taking all the system time..?
Date: Wed, 30 Jan 2002 17:49:15 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805964@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805950@msgid-missing>

duraid@fl.net.au wrote:
> it once declared upon high that longs shall always be 32 bits, long longs
> shall always be 64 bits, and ints shall be Whatever Length Is Most
> Efficiently Dealt With By The Hardware(tm)?

I believe the "long long" was a non-standard implementation for
32-bit compilers to declare/access 64-bit data structures.

And for LP64, ints are guaranteed to be 32-bits or it would have been
called ILP64.

grant


  parent reply	other threads:[~2002-01-30 17:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30  5:48 [Linux-ia64] What's taking all the system time..? Duraid Madina
2002-01-30  6:21 ` Stephane Eranian
2002-01-30  6:26 ` Niels Christiansen
2002-01-30  6:44 ` duraid
2002-01-30  6:46 ` duraid
2002-01-30  6:54 ` Stephane Eranian
2002-01-30  6:58 ` Niels Christiansen
2002-01-30  7:02 ` Niels Christiansen
2002-01-30  7:27 ` Niels Christiansen
2002-01-30  9:36 ` duraid
2002-01-30 10:04 ` [Linux-ia64] What's taking all the system time..? The unaligned accesses are! Duraid Madina
2002-01-30 17:43 ` [Linux-ia64] What's taking all the system time..? Boehm, Hans
2002-01-30 17:49 ` Grant Grundler [this message]
2002-01-30 18:04 ` Niels Christiansen
2002-01-30 21:57 ` Jim Wilson
2002-02-01 21:28 ` David Mosberger

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=marc-linux-ia64-105590698805964@msgid-missing \
    --to=grundler@cup.hp.com \
    --cc=linux-ia64@vger.kernel.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.