From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r114515: * bytecode.c (exec_byte_code): Use some more volatile variables
Date: Fri, 04 Oct 2013 10:05:21 -0400 [thread overview]
Message-ID: <jwvpprlcevj.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <E1VRzF1-0000fg-0n@vcs.savannah.gnu.org> (Paul Eggert's message of "Fri, 04 Oct 2013 06:51:59 +0000")
Could we declare those new vars just locally within the Bpushhandler code?
Stefan
> + Lisp_Object *volatile vectorp_volatile;
> #ifdef BYTE_CODE_SAFE
> - ptrdiff_t const_length;
> - Lisp_Object *stacke;
> - ptrdiff_t bytestr_length;
> + ptrdiff_t volatile const_length;
> + Lisp_Object *volatile stacke;
> + ptrdiff_t volatile bytestr_length;
> #endif
> struct byte_stack stack;
> + struct byte_stack volatile stack_volatile;
> Lisp_Object *top;
> Lisp_Object result;
> enum handlertype type;
> @@ -1119,16 +1122,25 @@
> PUSH_HANDLER (c, tag, type);
> c->bytecode_dest = dest;
> c->bytecode_top = top;
> + count_volatile = count;
> + stack_volatile = stack;
> + vectorp_volatile = vectorp;
> +
> if (sys_setjmp (c->jmp))
> {
> struct handler *c = handlerlist;
> + int dest;
> top = c->bytecode_top;
> - int dest = c->bytecode_dest;
> + dest = c->bytecode_dest;
> handlerlist = c->next;
> PUSH (c->val);
> CHECK_RANGE (dest);
> + stack = stack_volatile;
> stack.pc = stack.byte_string_start + dest;
> }
> +
> + count = count_volatile;
> + vectorp = vectorp_volatile;
> NEXT;
> }
> _______________________________________________
> Emacs-diffs mailing list
> Emacs-diffs@gnu.org
> https://lists.gnu.org/mailman/listinfo/emacs-diffs
parent reply other threads:[~2013-10-04 14:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1VRzF1-0000fg-0n@vcs.savannah.gnu.org>]
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=jwvpprlcevj.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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.