unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: crash: x_error_quitter
Date: Wed, 16 May 2007 23:42:40 +0200	[thread overview]
Message-ID: <85k5v830of.fsf@lola.goethe.zz> (raw)
In-Reply-To: <u4pmcejbw.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 16 May 2007 21\:04\:19 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: David Kastrup <dak@gnu.org>
>> Date: Wed, 16 May 2007 08:58:42 +0200
>> Cc: cyd@stupidchicken.com, jan.h.d@swipnet.se, emacs-devel@gnu.org
>> 
>> I think that if we are compiling with -g, we should also enable the
>> -fno-crossjumping option.  Drawback is that this will cause slightly
>> different code to be produced.
>
> Why not use -fno-crossjumping even if we compile without -g?  I can
> hardly believe this will cause any visible slowdown, as Emacs does not
> have tight inner loops anywhere.

We are not even talking tight inner loops here.  We are talking calls
of functions that never return.  Those can't happen too often (unless
there is some exception mechanism involved, or garbage compaction of
the stack, a tactique that some Scheme runtimes use for implementing
continuations), or the stack will overflow.

This is just a mechanism for squeezing out a few bytes.

Using -fno-crossjumping always (when supported by the compiler, of
course) would probably save us some dozen man hours of erroneous
post-mortem debugging.  The main disadvantage is that it makes the
compilation look ugly, as if Emacs were some special application
needing special compiler options.  In my opinion, crossjumping should
likely only be enabled for -O5 or greater.  Something like that.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

      reply	other threads:[~2007-05-16 21:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 18:05 crash: x_error_quitter sds
2007-05-11 18:48 ` Richard Stallman
2007-05-11 18:56   ` Sam Steingold
2007-05-12 16:47     ` Richard Stallman
2007-05-11 20:02 ` Chong Yidong
2007-05-12  6:51   ` Jan Djärv
2007-05-12 16:47   ` Richard Stallman
2007-05-12 23:31     ` Chong Yidong
2007-05-12 23:36       ` Chong Yidong
2007-05-13 13:29         ` Jan Djärv
2007-05-13 13:41         ` Chong Yidong
2007-05-13 13:00       ` Jan Djärv
2007-05-13 13:52         ` Chong Yidong
2007-05-13 15:33           ` Jan Djärv
2007-05-14  8:09           ` Richard Stallman
2007-05-14  8:40             ` David Kastrup
2007-05-15  9:47               ` Richard Stallman
2007-05-15  9:59                 ` David Kastrup
2007-05-16  1:39                   ` Richard Stallman
2007-05-16  6:58                     ` David Kastrup
2007-05-16 14:32                       ` Richard Stallman
2007-05-16 18:04                       ` Eli Zaretskii
2007-05-16 21:42                         ` David Kastrup [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

  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=85k5v830of.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=eliz@gnu.org \
    --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).