From: Dmitry Antipov <dmantipov@yandex.ru>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: gpion@lfdj.com, Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Broken !GC_MARK_STACK [Re: conservative stack scanning]
Date: Sat, 12 Jan 2013 06:15:57 +0400 [thread overview]
Message-ID: <50F0C75D.1040607@yandex.ru> (raw)
In-Reply-To: <50F0C1A4.40309@cs.ucla.edu>
On 01/12/2013 05:51 AM, Paul Eggert wrote:
> On 01/11/2013 11:51 AM, Stefan Monnier wrote:
>> Shouldn't we just enable conservative stack scanning for
>> all architectures?
>
> Yes, we should give it a try. If it doesn't work we can revert.
> If it does work, we can simplify Emacs and this will help prevent
> future bugs like Bug#13408.
Argh, current trunk is broken with !GC_MARK_STACK anyway:
1) I don't know why this isn't in the trunk:
http://lists.gnu.org/archive/html/emacs-devel/2011-11/txtjY_VzSBijo.txt
2) My stuff from commit 111073 breaks !GC_MARK_STACK because Lisp_Objects
referenced from Lisp_Misc_Save_Value are marked only if GC_MARK_STACK :-(.
Dmitry
next prev parent reply other threads:[~2013-01-12 2:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 17:46 bug#13408: Emacs pretest 24.2.92 - compilation error on AIX 5.3 using gcc 4.7-2 Gilles Pion
2013-01-11 6:26 ` Glenn Morris
2013-01-11 8:24 ` Eli Zaretskii
2013-01-11 8:03 ` Paul Eggert
2013-01-11 9:15 ` Eli Zaretskii
2013-01-11 19:11 ` Paul Eggert
2013-01-11 19:51 ` conservative stack scanning (was: Re: bug#13408: Emacs pretest 24.2.92 - compilation error on AIX 5.3 using gcc 4.7-2) Stefan Monnier
2013-01-12 1:51 ` conservative stack scanning Paul Eggert
2013-01-12 2:15 ` Dmitry Antipov [this message]
2013-01-12 6:19 ` Broken !GC_MARK_STACK [Re: conservative stack scanning] Paul Eggert
2013-01-14 9:59 ` Dmitry Antipov
2013-01-12 4:23 ` conservative stack scanning Stefan Monnier
2013-01-12 5:22 ` 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=50F0C75D.1040607@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gpion@lfdj.com \
--cc=monnier@iro.umontreal.ca \
/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.