all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: lekktu@gmail.com, 12446@debbugs.gnu.org
Subject: bug#12446: port better to POSIX hosts lacking _setjmp
Date: Sat, 15 Sep 2012 10:12:53 +0300	[thread overview]
Message-ID: <83sjaju5ca.fsf@gnu.org> (raw)
In-Reply-To: <5053A177.1020608@cs.ucla.edu>

> Date: Fri, 14 Sep 2012 14:28:23 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: 12446@debbugs.gnu.org, lekktu@gmail.com
> 
> On 09/14/2012 01:30 PM, Eli Zaretskii wrote:
> > Why not simply switch to using
> > ANSI- and Posix-standard setjmp/longjmp?
> 
> Because longjmp might alter the signal mask,
> and it might not.  POSIX doesn't say either way,
> platforms differ in this respect, and the
> differences can mess things up and slow things down.

Can you elaborate?  On which platforms does longjmp change the signal
mask and how, and in what ways can this "mess things up and slow
things down"?





  parent reply	other threads:[~2012-09-15  7:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 19:44 bug#12446: port better to POSIX hosts lacking _setjmp Paul Eggert
2012-09-14 20:30 ` Eli Zaretskii
2012-09-14 21:28   ` Paul Eggert
2012-09-15  7:10     ` Paul Eggert
2012-09-15  8:08       ` Eli Zaretskii
2012-09-15  8:46         ` Paul Eggert
2012-09-15  9:41           ` Eli Zaretskii
2012-09-15 10:06             ` Paul Eggert
2012-09-15  7:12     ` Eli Zaretskii [this message]
2012-09-15  7:50       ` Paul Eggert
2012-09-15  8:28         ` Eli Zaretskii
2012-09-15  8:55           ` Paul Eggert
2012-09-15  9:44             ` Eli Zaretskii
2012-09-15 10:00               ` Paul Eggert
2012-09-15 10:27                 ` Eli Zaretskii
2012-09-15 20:26                   ` Paul Eggert

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=83sjaju5ca.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12446@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=lekktu@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.