From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: lekktu@gmail.com, rms@gnu.org, 12450@debbugs.gnu.org
Subject: bug#12450: Remove configure's --without-sync-input option.
Date: Sun, 16 Sep 2012 11:53:33 +0300 [thread overview]
Message-ID: <83627es60i.fsf@gnu.org> (raw)
In-Reply-To: <50558F2C.9090304@cs.ucla.edu>
> Date: Sun, 16 Sep 2012 01:34:52 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: rms@gnu.org, 12450@debbugs.gnu.org, lekktu@gmail.com
>
> > we cannot be sure whether its non-invocation on
> > SYNC_INPUT platforms isn't a simple omission, because most Posix
> > platforms use neither gmalloc nor ralloc.c.
>
> I'm not sure how you're counting, but many POSIXish systems use gmalloc.
> These include FreeBSD, NetBSD, OpenBSD, HP-UX, AIX, and IRIX.
Most people here use GNU/Linux, which doesn't. I don't know what
Stefan used to test SYNC_INPUT.
> Of course it's possible that there are memory allocation glitches
> on such systems, glitches that we haven't caught in the four years we've
> been using SYNC_INPUT. But any such glitches would be an independent
> bug, i.e., a bug that we should fix independently of whether we remove
> --without-sync-input.
I'm not talking about removing the option, I'm talking about what
should and shouldn't be done as part of that removal. You suggest
removing some part whose significance we do not understand in full.
We can either dig into the related code and our memories and
understand those parts, or we can play it safe and not remove the
parts we don't understand. Any third possibility would be acting
irresponsibly on our part.
> And the glitches can't be that serious, or we'd have noticed them
> before now.
See bug #12242, for a demonstration of how easy to notice such bugs.
next prev parent reply other threads:[~2012-09-16 8:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 7:54 bug#12450: Remove configure's --without-sync-input option Paul Eggert
2012-09-15 9:32 ` Eli Zaretskii
2012-09-15 10:14 ` Paul Eggert
2012-09-15 11:03 ` Eli Zaretskii
2012-09-15 19:59 ` Paul Eggert
2012-09-15 20:15 ` Eli Zaretskii
2012-09-15 20:31 ` Paul Eggert
2012-09-16 6:33 ` Eli Zaretskii
2012-09-16 7:47 ` Paul Eggert
2012-09-16 8:05 ` Eli Zaretskii
2012-09-16 8:17 ` Paul Eggert
2012-09-16 8:21 ` Eli Zaretskii
2012-09-16 8:24 ` Eli Zaretskii
2012-09-16 8:34 ` Paul Eggert
2012-09-16 8:53 ` Eli Zaretskii [this message]
2012-09-15 21:12 ` Stefan Monnier
2012-09-16 5:55 ` Eli Zaretskii
2012-09-16 14:58 ` Stefan Monnier
2012-09-16 15:45 ` Eli Zaretskii
2012-09-16 16:30 ` Paul Eggert
2012-09-16 18:40 ` Eli Zaretskii
2012-09-16 19:55 ` Jan Djärv
2012-09-16 18:37 ` Stefan Monnier
2012-09-16 9:33 ` Daniel Colascione
2012-09-16 10:43 ` Eli Zaretskii
2012-09-16 15:10 ` Stefan Monnier
2012-09-16 15:40 ` Eli Zaretskii
2012-09-15 22:18 ` Richard Stallman
2012-09-16 3:15 ` Paul Eggert
2012-09-16 6:10 ` Eli Zaretskii
2012-09-16 8:23 ` Paul Eggert
2012-09-16 8:32 ` Eli Zaretskii
2012-09-16 21:48 ` Paul Eggert
2012-09-17 7:42 ` Eli Zaretskii
2012-09-21 20:50 ` Paul Eggert
2012-09-22 9:03 ` Eli Zaretskii
2012-09-22 9:34 ` Paul Eggert
2012-09-22 9:50 ` Eli Zaretskii
2012-09-22 10:01 ` Paul Eggert
2012-09-16 9:52 ` Daniel Colascione
2012-09-16 10:44 ` Eli Zaretskii
2012-09-16 10:56 ` Daniel Colascione
2012-09-17 7:41 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83627es60i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12450@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=lekktu@gmail.com \
--cc=rms@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 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.