From: Joseph Mingrone <jrm@ftfl.ca>
To: Pip Cet <pipcet@gmail.com>
Cc: Mattias <mattiase@acm.org>, Lars Ingebrigtsen <larsi@gnus.org>,
Vitalie Spinu <spinuvit@gmail.com>,
46912@debbugs.gnu.org
Subject: bug#46912: 28.0.50; Byte compiled defvar with lexical binding throws (void-variable foo)
Date: Thu, 04 Mar 2021 19:15:27 -0400 [thread overview]
Message-ID: <868s721pf4.fsf@phe.ftfl.ca> (raw)
In-Reply-To: <CAOqdjBdtC2vQTPyu9j05jmi8V7VtJYbdDJqPNM_NdW0V8cvRdw@mail.gmail.com> (Pip Cet's message of "Thu, 4 Mar 2021 21:08:13 +0000")
On Thu, 2021-03-04 at 21:08, Pip Cet <pipcet@gmail.com> wrote:
> On Thu, Mar 4, 2021 at 8:48 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>> Joseph Mingrone <jrm@ftfl.ca> writes:
>> > I think the problem was introduced before 9b4a2dd (2021-02-14). That
>> > was the last snapshot that I was running and I'm pretty sure I saw the
>> > problem then. If I can find time tonight, I'll try to confirm that.
>> Great; bisecting this would be very helpful.
> Absolutely.
>> Pip Cet <pipcet@gmail.com> writes:
>> > I can reproduce it, three, but I can also reproduce it with the change
>> > I think you're referring to reverted.
>> Sorry about that; it was a stab in the dark using the "the one who
>> touched it last" principle. :-/
> Not a problem at all. In fact, I've taken a look and it seems
> byte-optimize-form-code-walker simply ignores the value form in a
> defvar now..
> So I suspect it's commit 83983b6b7a115474572973b62eb5e42251713e63, I'm
> cc'ing Mattias, and I suspect this patch might help (but I've only
> done one quick test).
> Pip
With this patch applied to 20596a5, I still see the problems Vitalie
reported.
Joe
next prev parent reply other threads:[~2021-03-04 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 0:14 bug#46912: 28.0.50; Byte compiled defvar with lexical binding throws (void-variable foo) Vitalie Spinu
2021-03-04 18:03 ` Joseph Mingrone
2021-03-04 20:09 ` Lars Ingebrigtsen
2021-03-04 20:17 ` Joseph Mingrone
2021-03-04 20:48 ` Lars Ingebrigtsen
2021-03-04 21:08 ` Pip Cet
2021-03-04 23:15 ` Joseph Mingrone [this message]
2021-03-05 2:52 ` Pip Cet
2021-03-05 3:22 ` Joseph Mingrone
2021-03-05 8:27 ` Vitalie Spinu
2021-03-05 9:10 ` Mattias Engdegård
2021-03-05 9:56 ` Pip Cet
2021-03-04 20:21 ` Pip Cet
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=868s721pf4.fsf@phe.ftfl.ca \
--to=jrm@ftfl.ca \
--cc=46912@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=pipcet@gmail.com \
--cc=spinuvit@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).