all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattiase@acm.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	62537@debbugs.gnu.org,
	Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Subject: bug#62537: Error compiling emacs master with native compilation activated
Date: Thu, 6 Apr 2023 12:42:18 +0200	[thread overview]
Message-ID: <775940BE-8158-4AFE-8AA1-5FBA4D7C2C95@acm.org> (raw)
In-Reply-To: <xjfmt3mi6v6.fsf@ma.sdf.org>

5 apr. 2023 kl. 19.19 skrev Andrea Corallo <akrl@sdf.org>:

> 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.

Actually I don't think I can prove that the LAP code will never have the pattern that triggered the bug in Emacs 29; nothing prevents it in principle from occurring anyway.

It doesn't seem safe to keep the buggy limplification in that branch -- I suggest we remove the switch-eliminating optimisation in comp.el altogether just in case. What do you think?






      parent reply	other threads:[~2023-04-06 10:42 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
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 [this message]

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=775940BE-8158-4AFE-8AA1-5FBA4D7C2C95@acm.org \
    --to=mattiase@acm.org \
    --cc=62537@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=eliz@gnu.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 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.