From: "Mattias Engdegård" <mattiase@acm.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 53071-done@debbugs.gnu.org, Philipp <p.stephani2@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Paul Pogonyshev <pogonyshev@gmail.com>
Subject: bug#53071: 28.0.90; Emacs 28 regression: incorrect code generation for complex pcase forms?
Date: Wed, 12 Jan 2022 17:03:44 +0100 [thread overview]
Message-ID: <653D1A81-3A8F-4964-8A80-4C84F8C2A07A@acm.org> (raw)
In-Reply-To: <D3DDF097-3AD4-4C00-B6D0-9DA586BCB135@acm.org>
12 jan. 2022 kl. 16.35 skrev Mattias Engdegård <mattiase@acm.org>:
>
> 12 jan. 2022 kl. 15.10 skrev Michael Heerdegen <michael_heerdegen@web.de>:
>
>>> commit 1362a9fec4dff341a84c881ac17dbf1ee2cf82fd
>>> Author: Mattias Engdegård <mattiase@acm.org>
>>> Date: Fri Mar 5 20:21:01 2021 +0100
>>>
>>> Make lambda-lifting work again
>>
>> Not that again. Let's CC Mattias then.
>
> Again? In any case, that change only fixed a typo in earlier code by Stefan. More likely to be a logic error in the parent change (a350ae058cae), or in edebug.
No, you're right, it's bug#51982 again. I've backported the fix from master, which we should have done from the beginning. Paul, I'd like to say on record that listening to you would have saved us much time.
Thanks for bringing this to my attention!
next prev parent reply other threads:[~2022-01-12 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 9:36 bug#53071: 28.0.90; Emacs 28 regression: incorrect code generation for complex pcase forms? Philipp Stephani
2022-01-12 2:19 ` Philipp
2022-01-12 14:10 ` Michael Heerdegen
2022-01-12 15:35 ` Mattias Engdegård
2022-01-12 16:03 ` Mattias Engdegård [this message]
2022-01-12 16:58 ` Eli Zaretskii
2022-01-12 19:09 ` Mattias Engdegård
2022-01-12 19:33 ` Eli Zaretskii
2022-01-12 19:37 ` Philipp Stephani
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=653D1A81-3A8F-4964-8A80-4C84F8C2A07A@acm.org \
--to=mattiase@acm.org \
--cc=53071-done@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=p.stephani2@gmail.com \
--cc=pogonyshev@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).