From: Alan Mackenzie <acm@muc.de>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 54990@debbugs.gnu.org
Subject: bug#54990: Byte compiler bug
Date: Thu, 21 Apr 2022 09:49:58 +0000 [thread overview]
Message-ID: <YmEoxrdWQtOpv5ey@ACM> (raw)
In-Reply-To: <YmBgFdkboHkUvEsU@ACM>
Hello again, Mattias.
On Wed, Apr 20, 2022 at 19:33:41 +0000, Alan Mackenzie wrote:
> On Mon, Apr 18, 2022 at 17:43:46 +0200, Mattias Engdegård wrote:
> > 18 apr. 2022 kl. 12.48 skrev Alan Mackenzie <acm@muc.de>:
[ .... ]
> > Why did this bug only affect `compile-defun`, not `byte-compile` or
> > `byte-compile-file`? The change is in code common to all three.
> Yes, I find that intriguing, too. I'm meaning to try to find out why
> that was the case. The first priority was to fix the bug. The
> differences between the ways the compiler was called might hide further
> bugs, though.
This is now clear. byte-compile is compiling a form, not source code,
so unless the form was read with symbol positions, it won't have them.
In byte-compile-file, symbol positions are stripped as the byte code
gets output to the file.elc. So the symbol positions were not in the
..elc.
Only in compile-defun were there positions, and they "survived".
So I don't think there is a problem here.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-04-21 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 12:31 bug#54990: Byte compiler bug Alan Mackenzie
2022-04-17 13:02 ` Lars Ingebrigtsen
2022-04-17 13:53 ` Alan Mackenzie
2022-04-17 14:32 ` Mattias Engdegård
2022-04-18 10:48 ` Alan Mackenzie
2022-04-18 15:43 ` Mattias Engdegård
2022-04-20 19:33 ` Alan Mackenzie
2022-04-21 9:49 ` Alan Mackenzie [this message]
2022-05-02 13:45 ` Mattias Engdegård
2022-05-02 18:46 ` Alan Mackenzie
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=YmEoxrdWQtOpv5ey@ACM \
--to=acm@muc.de \
--cc=54990@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
/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).