From: Daniel Colascione <dancol@dancol.org>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>,
Aaron Jensen <aaronjensen@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>
Cc: 30364@debbugs.gnu.org, alan@idiocy.org, npostavs@gmail.com,
npostavs@users.sourceforge.net
Subject: bug#30364: 26.0.91; thread crash on macos
Date: Mon, 19 Feb 2018 09:29:49 -0800 [thread overview]
Message-ID: <3adcabd2-733e-fabf-7c2e-7032de42f5dd@dancol.org> (raw)
In-Reply-To: <ece6ee83-ff2e-85a6-9068-f5c41ee7fb9a@cs.ucla.edu>
On 02/19/2018 09:24 AM, Paul Eggert wrote:
> Eli Zaretskii wrote:
>>> Would you like me to vary it based on 32-bit vs 64-bit?
>> I think so, but I'd like to hear from others about this. Paul,
>> Andreas, could you please comment?
>
> A 64-bit Emacs should need more stack space than a 32-bit Emacs, yes. It
> wouldn't be double the space, since not everything on the stack is a
> pointer or an EMACS_INT. If you really want to fine-tune it you can also
> depend on the width of EMACS_INT. Getting it "just right" would be a bit
> tricky.
>
> 8 MiB/thread for 64-bit Emacs sounds OK to me. I wouldn't cheap out on
> 64-bit platforms.
What about just dedicating a thread to GC? We'd create it and have it
wait on a condition variable. Any thread could signal the CV, block, and
wait for GC to complete. It'd be pretty simple, I think, and unlike the
"always GC on main thread" proposal, it wouldn't force everything on the
main thread to be interruptible.
next prev parent reply other threads:[~2018-02-19 17:29 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 8:21 bug#30364: 26.0.91; thread crash on macos Aaron Jensen
2018-02-14 1:05 ` Noam Postavsky
2018-02-14 1:22 ` Aaron Jensen
2018-02-17 14:44 ` Noam Postavsky
2018-02-17 17:58 ` Aaron Jensen
2018-02-17 18:17 ` Eli Zaretskii
2018-02-17 18:40 ` Aaron Jensen
2018-02-17 18:55 ` Eli Zaretskii
2018-02-18 1:58 ` Aaron Jensen
2018-02-18 4:51 ` Eli Zaretskii
2018-02-18 4:54 ` Aaron Jensen
2018-02-18 16:45 ` Eli Zaretskii
[not found] ` <CAHyO48y+c21biWxQDTMvW2PkSKW6TzZVWQ94yUPN_4n3utDv5A@mail.gmail.com>
2018-02-18 18:25 ` Eli Zaretskii
2018-02-18 18:38 ` Aaron Jensen
2018-02-18 18:39 ` Aaron Jensen
2018-02-18 18:59 ` Aaron Jensen
2018-02-18 19:32 ` Eli Zaretskii
2018-02-18 19:49 ` Aaron Jensen
2018-02-18 20:15 ` Eli Zaretskii
2018-02-18 21:12 ` Aaron Jensen
2018-02-19 3:29 ` Eli Zaretskii
2018-02-19 17:24 ` Paul Eggert
2018-02-19 17:29 ` Daniel Colascione [this message]
2018-02-19 18:39 ` Eli Zaretskii
2018-02-19 18:33 ` Eli Zaretskii
2018-02-19 18:47 ` Aaron Jensen
2018-02-19 20:08 ` Paul Eggert
2018-02-19 20:16 ` Aaron Jensen
2018-02-25 20:52 ` Aaron Jensen
2018-02-27 17:30 ` Paul Eggert
2018-02-27 17:38 ` Aaron Jensen
2018-02-27 17:44 ` Paul Eggert
2018-02-28 5:33 ` Aaron Jensen
2018-02-28 15:33 ` Eli Zaretskii
2018-02-28 15:35 ` Aaron Jensen
2018-02-28 16:20 ` Eli Zaretskii
2018-02-28 17:32 ` Aaron Jensen
2018-02-28 17:38 ` Eli Zaretskii
2018-02-28 17:59 ` Aaron Jensen
2018-02-28 18:07 ` Aaron Jensen
2018-02-28 19:15 ` Paul Eggert
2018-02-28 20:36 ` Eli Zaretskii
2018-03-01 0:31 ` Paul Eggert
2018-03-01 8:37 ` Aaron Jensen
2018-05-13 15:13 ` Noam Postavsky
2018-05-13 16:26 ` Eli Zaretskii
2018-05-14 20:03 ` Paul Eggert
2018-02-28 16:19 ` Paul Eggert
2018-02-18 19:07 ` Eli Zaretskii
2018-02-18 19:04 ` Eli Zaretskii
2018-02-18 11:01 ` Alan Third
2018-02-17 18:23 ` Alan Third
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=3adcabd2-733e-fabf-7c2e-7032de42f5dd@dancol.org \
--to=dancol@dancol.org \
--cc=30364@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=alan@idiocy.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=npostavs@gmail.com \
--cc=npostavs@users.sourceforge.net \
--cc=schwab@linux-m68k.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).