From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 2790@emacsbugs.donarmstrong.com, Mike Coleman <tutufan@gmail.com>
Subject: bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Linux box
Date: Fri, 27 Mar 2009 12:21:57 +0100 [thread overview]
Message-ID: <m2ab77dxd6.fsf@igel.home> (raw)
In-Reply-To: <uprg4m1g8.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 26 Mar 2009 23:14:15 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Thu, 26 Mar 2009 16:01:51 -0500
>> From: Mike Coleman <tutufan@gmail.com>
>> Cc: 2790@emacsbugs.donarmstrong.com
>>
>> most-positive-fixnum gives
>>
>> 1152921504606846975 (#o37777777777, #xffffffff)
>
> That sounds like a bug: the decimal representation is like I'd expect
> on a 64-bit machine, but the octal and hex representations are like on
> a 32-bit machine. Strange...
22.1 had a buggy format that truncated numbers to the range of int. I
fixed some bugs here for 22.2.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-03-27 11:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 15:50 bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Linux box Mike Coleman
2009-03-26 19:58 ` Eli Zaretskii
2009-03-26 21:01 ` Mike Coleman
2009-03-26 21:14 ` Eli Zaretskii
2009-03-26 21:33 ` Mike Coleman
2009-03-27 0:32 ` Stefan Monnier
2009-03-27 0:39 ` Mike Coleman
2009-03-27 3:08 ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Linux Stefan Monnier
2009-03-27 16:29 ` Mike Coleman
2009-03-27 8:46 ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Linux box Eli Zaretskii
2009-03-27 11:21 ` Andreas Schwab [this message]
2009-03-27 4:59 ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit GNU/Linux box Richard M Stallman
2009-03-27 16:27 ` Mike Coleman
2009-03-27 17:42 ` Eli Zaretskii
2009-03-28 2:12 ` Stefan Monnier
2009-03-28 5:24 ` Mike Coleman
2009-03-29 19:59 ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Stefan Monnier
2009-03-28 8:45 ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit GNU/Linux box Eli Zaretskii
2009-03-28 11:12 ` Andreas Schwab
2009-03-28 12:03 ` Eli Zaretskii
2009-03-28 12:40 ` Andreas Schwab
2009-03-28 13:52 ` Eli Zaretskii
2009-03-29 20:13 ` Stefan Monnier
2009-03-29 20:10 ` Stefan Monnier
2009-03-29 20:44 ` Andreas Schwab
2009-03-30 0:59 ` Stefan Monnier
2009-03-30 8:08 ` Andreas Schwab
2009-03-30 13:01 ` Stefan Monnier
2009-03-30 13:22 ` Andreas Schwab
2009-03-29 2:15 ` Richard M Stallman
2009-03-29 20:14 ` Stefan Monnier
2009-03-28 15:17 ` Richard M Stallman
2009-03-28 16:27 ` Mike Coleman
[not found] ` <mailman.4163.1238258635.31690.bug-gnu-emacs@gnu.org>
2009-03-31 14:17 ` Ted Zlatanov
2011-09-11 22:10 ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Linux box Lars Magne Ingebrigtsen
2011-09-12 2:59 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ab77dxd6.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=2790@emacsbugs.donarmstrong.com \
--cc=eliz@gnu.org \
--cc=tutufan@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).