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: Wed, 5 Apr 2023 23:46:09 +0200 [thread overview]
Message-ID: <B382826C-24BB-4EF4-AF8C-27AA2DF3EE70@acm.org> (raw)
In-Reply-To: <xjffs9ehw46.fsf@ma.sdf.org>
5 apr. 2023 kl. 23.12 skrev Andrea Corallo <akrl@sdf.org>:
>> (Perhaps we should do something like that in the LAP optimiser. Wonder how common the opportunity is though.)
>
> Yeah might be a good idea even if I don't know how common this condition
> is.
Experimentally adding a LAP optimiser rule for it resulted in no matches during a complete lisp recompilation, so it's safe to say that it's not very common.
I'm not going to bother, but perhaps your code works on something that has undergone further transformations and is thus more likely to trigger the rule?
>> (apply #'= (hash-table-values jmp-table))
>>
>> which is arguably clearer and definitely shorter.
>
> True but with the downside that it conses.
More than the current code?
next prev parent reply other threads:[~2023-04-05 21:46 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 [this message]
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=B382826C-24BB-4EF4-AF8C-27AA2DF3EE70@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 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).