From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, erik quanstrom <quanstro@quanstro.net>
Subject: [9fans] bizarre 64bit problem
Date: Fri, 13 Jan 2006 23:12:59 -0600 [thread overview]
Message-ID: <20060114051259.DD11D3256A@dexter-peak.quanstro.net> (raw)
In-Reply-To: <20060114040224.6C1231140ED@dexter-peak.quanstro.net>
gcc is taking each 32bit half as a signed long. i believe that this is the
correct solution for gcc:
#define GBIT64(p) ((vlong)((ulong)(p)[0]|((p)[1]<<8)|((p)[2]<<16)|((p)[3]<<24)) |\
((vlong)((ulong)(p)[4]|((p)[5]<<8)|((p)[6]<<16)|((p)[7]<<24)) << 32))
i'd be curious what other compilers do with this.
- erik
erik quanstrom <quanstro@quanstro.net> writes
|
| this is on p9p with gcc-3.4.4 on a pentiumIII-coppermine.
|
| i've been trying to verify changes in tapefs/tarfs to support
| files in a tar archive > 2G. however, i get this:
|
| ; 9p ls tapefs
| --rw-r--r-- M 0 0 0 -1864421376 Jan 13 09:50 big1.tar
|
[etc]
prev parent reply other threads:[~2006-01-14 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 4:02 erik quanstrom
2006-01-14 5:12 ` erik quanstrom [this message]
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=20060114051259.DD11D3256A@dexter-peak.quanstro.net \
--to=quanstro@quanstro.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).