From: Andrea Corallo <acorallo@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, 67141@debbugs.gnu.org
Subject: bug#67141: 30.0.50; Missing element in the backtrace
Date: Mon, 20 Nov 2023 13:16:39 -0500 [thread overview]
Message-ID: <yp1edgk47eg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvedgkxr72.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 20 Nov 2023 12:52:27 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> If you want then I think we should consider this bug not only native
>> comp related, as I explained we have this issue since long time in
>> other circumstances.
>
> I think it's qualitatively different, but yes, this is not the only
> occurrence of the problem. AFAICT, we have 3 different cases:
>
> A. Native compiled code making a "direct call" to a C primitive.
> B. ELisp primitives with their own bytecode.
> C. C code calling `Ffoo` instead of `Ffuncall (Qfoo, ...)`.
>
> (B) and (C) have been with us for ever. They also suffer from being
> unaffected by advice. (A) on the other hand is new, but obeys advice.
>
> I think (C) is qualitatively very different from (A) because
> (C) can be fixed by hand whenever we decide that it's a problem,
Well ATM we can fix A by hand as well with a (declare (speed 0)) in the
calling function. Admittedly would be nice to have a more narrowed way
to handle this at call site. I'd e in favor of adding it. Do you think
this would be sufficient?
Andrea
next prev parent reply other threads:[~2023-11-20 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 22:29 bug#67141: 30.0.50; Missing element in the backtrace Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-13 14:03 ` Eli Zaretskii
2023-11-13 16:27 ` Andrea Corallo
2023-11-16 9:35 ` Andrea Corallo
2023-11-17 19:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-17 20:48 ` Andrea Corallo
2023-11-17 21:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-20 8:55 ` Andrea Corallo
2023-11-20 12:12 ` Eli Zaretskii
2023-11-20 13:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-20 15:13 ` Andrea Corallo
2023-11-20 17:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-20 18:16 ` Andrea Corallo [this message]
2023-11-20 18:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-20 21:01 ` Mattias Engdegård
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=yp1edgk47eg.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=67141@debbugs.gnu.org \
--cc=eliz@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 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).