From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: mi-ebugs@kismala.com, mattiase@acm.org, monnier@iro.umontreal.ca,
61504@debbugs.gnu.org
Subject: bug#61504: 29.0.60; executing byte-code from previous build causes SIGSEGV crash
Date: Tue, 14 Feb 2023 19:16:21 +0200 [thread overview]
Message-ID: <83fsb8cgm2.fsf@gnu.org> (raw)
In-Reply-To: <0f053182b0078c2103a9@heytings.org> (message from Gregory Heytings on Tue, 14 Feb 2023 17:00:55 +0000)
> Date: Tue, 14 Feb 2023 17:00:55 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: Eli Zaretskii <eliz@gnu.org>, mi-ebugs@kismala.com,
> Stefan Monnier <monnier@iro.umontreal.ca>, 61504@debbugs.gnu.org
>
> > By the way, doesn't the patch switch the restoration order of narrowing
> > and restriction, respectively? Maybe it doesn't matter?
>
> Hmmm, that's a good question! The evaluation order of parameters is
> unspecified in C, so actually the order could be switched or not,
> depending on what the compiler chooses to do.
But you could rewrite the code so that the parameters are evaluated
one after the other, and only after that call Fcons. The compiler
could still change the order, but that would be less probable.
> That being said, AFAICS it doesn't matter in this case, indeed.
It is IME better to write code that doesn't trigger such questions to
begin with.
> Eli, OK to install?
With the change of order per the above, yes.
Thanks.
next prev parent reply other threads:[~2023-02-14 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 6:33 bug#61504: 29.0.60; executing byte-code from previous build causes SIGSEGV crash Istvan Marko
2023-02-14 9:29 ` Gregory Heytings
2023-02-14 13:29 ` Eli Zaretskii
2023-02-14 16:50 ` Mattias Engdegård
2023-02-14 17:00 ` Gregory Heytings
2023-02-14 17:16 ` Eli Zaretskii [this message]
2023-02-14 20:44 ` Gregory Heytings
2023-02-14 17:21 ` Mattias Engdegård
2023-02-14 20:46 ` Gregory Heytings
2023-02-14 20:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-14 20:47 ` Gregory Heytings
2023-02-14 15:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-14 16:00 ` Gregory Heytings
2023-02-14 16:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-14 16:51 ` Gregory Heytings
2023-02-14 17:36 ` Istvan Marko
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=83fsb8cgm2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61504@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=mattiase@acm.org \
--cc=mi-ebugs@kismala.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.