From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: erroneous byte-compilation during build process?
Date: Tue, 26 Dec 2006 22:00:10 -0500 [thread overview]
Message-ID: <E1GzP1W-0006KE-IG@fencepost.gnu.org> (raw)
In-Reply-To: <87hd48p6np.fsf@escher.local.home> (message from Stephen Berman on Tue, 02 May 2006 21:29:14 +0200)
I am going through messages which I failed to handle during the past
year, and came across yours.
Because of this, it occurred to me that the error might not
be in recentf.el but in recentf.elc. So I made a fresh
byte-compilation of the source file and copied it to the install
directory and loaded recentf, making sure the conditions that give
rise to error were satisfied, and sure enough, the error failed to
occur. Then I reinstalled the original byte-compiled file and
repeated the test, and got the error again. So I conclude that the
recentf.elc made by building Emacs is somehow erroneous.
Does this still happen? Can you make it happen? Did we ever make a
change that should have fixed it?
It is clear that there was a miscompilation. There's a difference in
the bytecode of the two versions of the function recentf-open-files,
as well as in the arguments. I think that the function
tree-widget-set-theme got open coded in one of the two versions
but was called with a function call in the other.
prev parent reply other threads:[~2006-12-27 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 19:29 erroneous byte-compilation during build process? Stephen Berman
2006-05-02 19:46 ` Stuart D. Herring
2006-05-02 21:56 ` Stephen Berman
2006-12-27 3:00 ` Richard Stallman [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=E1GzP1W-0006KE-IG@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.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 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.