unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: emacs floating point error during dump?
Date: Tue, 08 Jul 2003 09:21:49 -0400	[thread overview]
Message-ID: <200307081321.h68DLnC3009346@rum.cs.yale.edu> (raw)
In-Reply-To: buo65md4ye6.fsf@mcspd15.ucom.lsi.nec.co.jp

> Anyone else see this when compiling CVS emacs?
> 
>    LC_ALL=C ./temacs -batch -l loadup dump
>    emacs: Invalid hash table rehash size: 5.30239915e-315
>    make[1]: *** [emacs] Error 1

My GC changes mostly affect handling of floating point values, so
it sounds like a good candidate.  But the above is useless for any
serious debugging, of course.

I'm trying to install my GC patches in small increments so that binary
search in the version space can point to reasonably small changes.
Please try to find out which patch to alloc.c leads to the above problem
(if any).  Also we need backtrace and stuff, of course.

Also don't forget that the makefile dependency rules for lisp.h are
missing, so you need to `rm src/*.o' because I've changed the representation
of floating point numbers.


	Stefan

  parent reply	other threads:[~2003-07-08 13:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08  1:09 emacs floating point error during dump? Miles Bader
2003-07-08  1:51 ` Luc Teirlinck
2003-07-08  3:38 ` Simon Josefsson
2003-07-08 13:21 ` Stefan Monnier [this message]
2003-07-09  1:33   ` Miles Bader
2003-07-09 13:44     ` Stefan Monnier
2003-07-10  2:17       ` Miles Bader
2003-07-10 11:32         ` Andreas Schwab
2003-07-11  3:50           ` Richard Stallman
2003-07-11 14:27             ` Stefan Monnier
2003-07-10 16:43       ` Richard Stallman
2003-07-11  0:04         ` Miles Bader
2003-07-11 13:42         ` Sam Steingold
2003-07-11 19:55           ` Richard Stallman
2003-07-11 20:27             ` Sam Steingold
2003-07-12  0:11               ` Kim F. Storm
2003-07-13  0:11               ` Richard Stallman
2003-07-13  0:30                 ` Sam Steingold
2003-07-13  1:32                   ` Miles Bader
2003-07-13  2:40                     ` Sam Steingold
2003-07-13  4:45                       ` David Kastrup
2003-07-13 17:34                         ` Richard Stallman
2003-07-13 17:37                           ` David Kastrup
2003-07-13 18:08                           ` Sam Steingold
2003-07-13  8:34                       ` Miles Bader
2003-07-13 10:35                         ` David Kastrup
2003-07-13 15:33                   ` Thien-Thi Nguyen
2003-07-13 23:06                   ` Stefan Monnier
2003-07-13 23:58                     ` Sam Steingold
2003-07-14  4:22                       ` Eli Zaretskii
2003-07-14 23:18                     ` Kim F. Storm
2003-07-15 11:02                       ` Richard Stallman

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=200307081321.h68DLnC3009346@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@cs.yale.edu \
    --cc=emacs-devel@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.
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).