From owner-freebsd-hackers Mon Apr 21 21:03:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA10929 for hackers-outgoing; Mon, 21 Apr 1997 21:03:41 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10921 for ; Mon, 21 Apr 1997 21:03:35 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA12801; Tue, 22 Apr 1997 13:33:25 +0930 (CST) From: Michael Smith Message-Id: <199704220403.NAA12801@genesis.atrad.adelaide.edu.au> Subject: Re: 64 bit number definitions? In-Reply-To: from Adrian Chadd at "Apr 22, 97 11:34:07 am" To: adrian@staff.psinet.net.au (Adrian Chadd) Date: Tue, 22 Apr 1997 13:33:24 +0930 (CST) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Adrian Chadd stands accused of saying: > > Is there anywhere a 64 bit type in C I can get my hands on? > (the longest i've seen builtin to the compiler is the unsigned long, but I > commonly write more than 4 gigabytes to tape at once). Either count in blocks, or use 'long long'. You can use 'off_t' if you prefer, as that may be a better match with lseek(). > Which reminds me, freebsd's GNU tar apparently uses an "int" type for > tot_written, that doesn't look like it cant count over 32k bytes. File a PR 8) > Adrian. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[