From: "Gary V. Vaughan" <gvaughan@oranda.demon.co.uk>
To: Per Bothner <bothner@cygnus.com>
Cc: EGCS mailing list <egcs@cygnus.com>, faber@dbai.tuwien.ac.at
Subject: Re: sizeof bool > sizeof int ?!?
Date: Fri, 10 Jul 1998 06:04:00 -0000 [thread overview]
Message-ID: <35A5F9E8.4CCE9333@oranda.demon.co.uk> (raw)
In-Reply-To: <199807091912.MAA15746@cygnus.com>
Per Bothner wrote:
>
> > Certainly code will run faster on most 32bit architectures using int's
> > (32 bits) rather than char's (8 bits), so it makes sense to use, e.g.
> > typedef int bool;
>
> Why stop there? We should by the same argument:
>
> typedef int short;
Surely you mean
#define short int
??? =)O|
...but yes, bizarre though it may sound, using shorts is a trading speed
for space (modulo the architecture instruction set), except perhaps in
the pedagogical case quoted earlier in the thread where the
proliferation of register width words in place of narrower types causes
additional page faults...
short array[10000];
anyone?
OTOH, please correct me if I am grossly misinformed.
Cheers,
Gary V. Vaughan
begin: vcard
fn: Gary Vaughan
n: Vaughan;Gary
org: Aethos Communication Systems ltd.
email;internet: gvaughan@oranda.demon.co.uk
tel;work: 01454 - 204411
x-mozilla-cpt: ;0
x-mozilla-html: FALSE
version: 2.1
end: vcard
next prev parent reply other threads:[~1998-07-10 6:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-03 6:15 Gerald Pfeifer
1998-07-05 2:58 ` Rask Ingemann Lambertsen
1998-07-06 4:08 ` Gary V. Vaughan
1998-07-09 12:13 ` Per Bothner
1998-07-10 6:04 ` Gary V. Vaughan [this message]
1998-07-06 14:48 ` Richard Hadsell
1998-08-13 17:47 ` Richard Hadsell
1998-08-20 9:57 ` Richard Hadsell
1998-08-20 20:37 ` Richard Henderson
1998-08-20 20:37 ` Per Bothner
1999-12-18 17:14 ` Gerald Pfeifer
1999-12-18 17:39 ` Mark Mitchell
1999-12-31 23:54 ` Mark Mitchell
1999-12-31 23:54 ` Gerald Pfeifer
1998-08-21 19:47 Mike Stump
1998-08-21 19:47 ` Richard Hadsell
1998-08-22 7:32 ` Jeroen Dobbelaere
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=35A5F9E8.4CCE9333@oranda.demon.co.uk \
--to=gvaughan@oranda.demon.co.uk \
--cc=bothner@cygnus.com \
--cc=egcs@cygnus.com \
--cc=faber@dbai.tuwien.ac.at \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).