From: Andrea Corallo <acorallo@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: 71555@debbugs.gnu.org, "Eli Zaretskii" <eliz@gnu.org>,
"Sévère Durand" <mmemmew@gmail.com>
Subject: bug#71555: 29.3.50; Native-compilation sets some variable to nil unexpectedly.
Date: Mon, 17 Jun 2024 06:15:48 -0400 [thread overview]
Message-ID: <yp1a5jjj2nf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <213EC279-4FB6-4F69-8BC4-1BE7A2AE7232@gmail.com> ("Mattias Engdegård"'s message of "Mon, 17 Jun 2024 12:08:51 +0200")
Mattias Engdegård <mattias.engdegard@gmail.com> writes:
>> I can't reproduce on master so the bug there is fixed.
>
> We don't actually know that, do we? The bug could just be hidden by other changes on master; the underlying error could still be present.
The type inference on master compared to 29 had many
changes/improvements so I'm not surprised at all of seeing this fixed.
> You know the native compiler code better than anyone else (and it's
> your time, of course), but it might be worth investigating. Do you
> have a way to dump intermediate representations at various stages?
Indeed see 'native-comp-verbose'.
Andrea
next prev parent reply other threads:[~2024-06-17 10:15 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
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 [this message]
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=yp1a5jjj2nf.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=71555@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattias.engdegard@gmail.com \
--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).