unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: "Sévère Durand" <mmemmew@gmail.com>
Cc: 71555@debbugs.gnu.org, eliz@gnu.org
Subject: bug#71555: 29.3.50; Native-compilation sets some variable to nil unexpectedly.
Date: Mon, 17 Jun 2024 04:00:08 -0400	[thread overview]
Message-ID: <yp1sexchud3.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAHg+Y3SikGA8ZMOsw=Kq-DDFCYOamiVnG1XepS=z1V4275AJKQ@mail.gmail.com> ("Sévère Durand"'s message of "Mon, 17 Jun 2024 15:32:16 +0800")

Sévère Durand <mmemmew@gmail.com> writes:

> Hello Mr.Andrea:
> Thanks for your reply and that of Mr.Gerd!
> I did not know that this was fixed on the master branch.  In this case, I think I can just add a notification to my
> package's readme, warning users that if they want to natively compile the package, then they should use the master branch
> (or the version 30) to avoid the bug.
> Thanks for the help!
> ---
> Durand

Hi Sévère,

another workaround that should work would be to add to your function:

(declare (speed 0))

This should work around the issue on all the already released releases.

Could you give it a try?

Thanks

  Andrea





  reply	other threads:[~2024-06-17  8:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 14:55 bug#71555: 29.3.50; Native-compilation sets some variable to nil unexpectedly Sévère Durand
2024-06-16 12:46 ` Gerd Möllmann
2024-06-17  7:25 ` Andrea Corallo
2024-06-17  7:32   ` Sévère Durand
2024-06-17  8:00     ` Andrea Corallo [this message]
2024-06-17 14:02       ` Sévère Durand
2024-06-17 14:38         ` Andrea Corallo
2024-06-17 14:41           ` Andrea Corallo
2024-06-17 12:00   ` Eli Zaretskii
2024-06-17 13:15     ` Andrea Corallo
2024-06-17 10:08 ` Mattias Engdegård
2024-06-17 10:15   ` Andrea Corallo
2024-06-17 10:58     ` Mattias Engdegård
2024-06-17 12:04   ` Eli Zaretskii

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=yp1sexchud3.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=71555@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mmemmew@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 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).