unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: 62537@debbugs.gnu.org
Cc: "Mattias Engdegård" <mattiase@acm.org>,
	"Eli Zaretskii" <eliz@gnu.org>,
	"Pedro Andres Aranda Gutierrez" <paaguti@gmail.com>
Subject: bug#62537: Error compiling emacs master with native compilation activated
Date: Wed, 05 Apr 2023 17:19:57 +0000	[thread overview]
Message-ID: <xjfmt3mi6v6.fsf@ma.sdf.org> (raw)
In-Reply-To: <664DC8F8-EEEC-4A90-A4F5-86C11378486C@acm.org> ("Mattias Engdegård"'s message of "Fri, 31 Mar 2023 17:14:58 +0200")

Gut I finally have a fix for this!

As we suspected was a bug in the native compiler limplification pass
triggered by the new LAP emitted.

fa669c4b17c fixes bootstrap --with-native-compilation=aot here and adds
a test, is now pushed to master.  In 29 the bug never showed up
(probably because the new LAP tweak is not it) so I guess it's better to
leave the code as it is.

Now we should finally have again bootstrap for both master and 29 clean,
so any issue we might see is unexpected to me.

Best Regards

  Andrea





  reply	other threads:[~2023-04-05 17:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  7:18 bug#62537: Error compiling emacs master with native compilation activated Pedro Andres Aranda Gutierrez
2023-03-30  8:50 ` Eli Zaretskii
2023-03-30  9:28 ` Andrea Corallo
2023-03-30  9:59   ` Pedro Andres Aranda Gutierrez
2023-03-30 10:37   ` Mattias Engdegård
2023-03-30 13:35     ` Andrea Corallo
2023-03-31 10:26       ` Andrea Corallo
2023-03-31 15:14         ` Mattias Engdegård
2023-04-05 17:19           ` Andrea Corallo [this message]
2023-04-05 20:51             ` Mattias Engdegård
2023-04-05 21:12               ` Andrea Corallo
2023-04-05 21:46                 ` Mattias Engdegård
2023-04-06 10:42             ` Mattias Engdegård

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=xjfmt3mi6v6.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=62537@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mattiase@acm.org \
    --cc=paaguti@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).