From: Eli Zaretskii <eliz@gnu.org>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: GC and stack marking
Date: Thu, 22 May 2014 05:43:46 +0300 [thread overview]
Message-ID: <83r43mmt25.fsf@gnu.org> (raw)
In-Reply-To: <CAFM41H2in6pyhLgpim+ZFkRO53-r2kK0Tr1DD3JCw13zzX5rLQ@mail.gmail.com>
> Date: Wed, 21 May 2014 16:49:22 -0400
> From: Barry OReilly <gundaetiapo@gmail.com>
> Cc: emacs-devel@gnu.org
>
> Even if we're only talking about the stack variables in the frames that are
> active during your particular problematic case (and perhaps in the idle
> Emacs GC case)?
I thought you were asking about having the compiler generate the code
to do that, which would then happen everywhere.
If you propose doing that selectively, I don't know how this would be
possible, since on the C level you don't have a way of telling how
much stack is allocated in a given function.
> Have you already ruled out whether stack_top_variable contributes one of
> the bytes in your false positive lookup in the mem_node tree?
Yes. I looked at all the local variables in that stack frame, and
their addresses on the stack are different from the one that triggers
the problem.
next prev parent reply other threads:[~2014-05-22 2:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 19:31 GC and stack marking Barry OReilly
2014-05-21 20:13 ` Eli Zaretskii
2014-05-21 20:49 ` Barry OReilly
2014-05-22 2:43 ` Eli Zaretskii [this message]
2014-05-22 3:12 ` Daniel Colascione
2014-05-22 5:37 ` David Kastrup
2014-05-22 13:57 ` Stefan Monnier
2014-05-22 15:49 ` Eli Zaretskii
2014-05-22 14:59 ` Barry OReilly
2014-05-22 17:03 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2014-05-19 16:31 Eli Zaretskii
2014-05-19 18:47 ` Paul Eggert
2014-05-19 19:14 ` Eli Zaretskii
2014-05-19 19:58 ` Paul Eggert
2014-05-19 20:03 ` Eli Zaretskii
2014-05-19 20:17 ` Paul Eggert
2014-05-20 16:37 ` Eli Zaretskii
2014-05-20 13:44 ` Stefan Monnier
2014-05-20 16:57 ` Eli Zaretskii
2014-05-20 17:54 ` Stefan Monnier
2014-05-20 19:28 ` Eli Zaretskii
2014-05-20 22:01 ` Stefan Monnier
2014-05-21 2:48 ` Eli Zaretskii
2014-05-21 3:01 ` Stefan Monnier
2014-05-21 15:39 ` Eli Zaretskii
2014-05-21 15:57 ` Dmitry Antipov
2014-05-21 16:06 ` Dmitry Antipov
2014-05-21 16:55 ` Eli Zaretskii
2014-05-21 16:53 ` Eli Zaretskii
2014-05-21 17:40 ` Stefan Monnier
2014-05-21 17:58 ` Eli Zaretskii
2014-05-22 15:20 ` Eli Zaretskii
2014-05-22 16:14 ` Stefan Monnier
2014-05-24 12:03 ` Eli Zaretskii
2014-05-20 19:12 ` Daniel Colascione
2014-05-20 19:43 ` Eli Zaretskii
2014-05-20 22:03 ` Stefan Monnier
2014-05-21 2:51 ` Eli Zaretskii
2014-05-31 6:31 ` Florian Weimer
2014-05-31 14:24 ` Stefan Monnier
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=83r43mmt25.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gundaetiapo@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.