all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 64526@debbugs.gnu.org
Subject: bug#64526: 30.0.50; jit-compilation and multiple function definitions
Date: Mon, 10 Jul 2023 07:52:10 -0400	[thread overview]
Message-ID: <yp11qhgugph.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvfs5wp0o9.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 10 Jul 2023 05:38:11 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> Package: Emacs
>>> Version: 30.0.50
>>>
>>>
>>> Say you have a file ~/tmp/foo.el:
>>>
>>>     ;;  -*- lexical-binding: t; -*-
>>>     (defun sm-foo1 (a) (list a 1))
>>>     (defun sm-foo1 (a) (list a 2))
>>>
>>> which you byte-compile into ~/tmp/foo.elc, and then you do:
>>>
>>>     emacs -Q -l ~/tmp/foo
>>>     M-: (sm-foo1 'a) RET
>>>
>>> you'll usually get `(a 2)` (and that's what we expect).  But if you enable
>>> native compilation and erase the `eln-cache` before trying it out you
>>> may get `(a 1)` because when the `.eln` file is reloaded on top of the
>>> `.elc` definitions, `comp--late-register-subr` will skip the second
>>> definition :-(
>>
>> Hi Stefan,
>>
>> are we sure about this? Is this reproducible?
>
> Yes, the above recipe reproduces it on my machine at least.

Okay, will look at thanks.

  Andrea





      reply	other threads:[~2023-07-10 11:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08  1:41 bug#64526: 30.0.50; jit-compilation and multiple function definitions Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-10  7:44 ` Andrea Corallo
2023-07-10  9:38   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-10 11:52     ` Andrea Corallo [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=yp11qhgugph.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=64526@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.