From: Andreas Jaeger <aj@suse.de>
To: Scott Robert Ladd <coyote@coyotegulch.com>
Cc: gcc@gcc.gnu.org
Subject: Re: 128-bit long long?
Date: Sun, 21 Mar 2004 17:37:00 -0000 [thread overview]
Message-ID: <m3oeqq1acs.fsf@gromit.moeb> (raw)
In-Reply-To: <405DB46B.80208@coyotegulch.com> (Scott Robert Ladd's message of "Sun, 21 Mar 2004 10:27:39 -0500")
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
Scott Robert Ladd <coyote@coyotegulch.com> writes:
> On a 64-bit AMD64 architecture, GCC defines long long as 64 bits, the
> same as a long.
>
> Given that certain 64-bit instructions (multiply) produce 128-bit
> results, doesn't it seem logical the long long be defined as 128 bits?
>
> I'm just wonder...
That will break too many "portable" software ;-(.
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-03-21 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 17:34 Scott Robert Ladd
2004-03-21 17:37 ` Andreas Jaeger [this message]
2004-03-21 18:02 ` Paolo Carlini
2004-03-21 20:27 ` Erik Trulsson
2004-03-21 20:52 ` Zack Weinberg
2004-03-21 21:11 ` Joseph S. Myers
2004-03-21 21:20 ` Scott Robert Ladd
2004-03-22 0:12 ` Paolo Carlini
2004-03-24 5:38 ` Richard B. Kreckel
2004-03-24 5:57 ` Paolo Carlini
2004-03-30 2:10 ` Jim Wilson
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=m3oeqq1acs.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=coyote@coyotegulch.com \
--cc=gcc@gcc.gnu.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 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).