From: Lynn Winebarger <owinebar@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56988@debbugs.gnu.org, Andrea Corallo <akrl@sdf.org>
Subject: bug#56988: Add call-interactively to "never optimize" list for native compilation
Date: Sun, 7 Aug 2022 07:32:24 -0400 [thread overview]
Message-ID: <CAM=F=bCaUv17=bFHppc4rsqm6REpqtvF0kK-2_QL4_92yOmJFw@mail.gmail.com> (raw)
In-Reply-To: <87a68iano8.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On Fri, Aug 5, 2022, 8:18 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Lynn Winebarger <owinebar@gmail.com> writes:
>
> > Isn't call-interactively only used in the context of requesting user
> > input? That would seem unlikely to benefit from optimization.
>
> Some interactive specs are pretty involved, and definitely benefit from
> being compiled, so we're not going to stop doing that.
Another possibility would be to ensure there is a standard pdmp file to use
for compiling, regardless of what is being used for the session calling the
compiler. I know that is not an issue at the moment, but I'm the canary in
the coal mine for when dumping additional native compiled units. That
feature is way too nice for someone to not get it in the trunk at some
point.
Lynn
[-- Attachment #2: Type: text/html, Size: 1302 bytes --]
prev parent reply other threads:[~2022-08-07 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 1:37 bug#56988: Add call-interactively to "never optimize" list for native compilation Lynn Winebarger
2022-08-05 10:07 ` Andrea Corallo
2022-08-05 12:13 ` Lynn Winebarger
2022-08-05 12:18 ` Lars Ingebrigtsen
2022-08-05 12:33 ` Lynn Winebarger
2023-06-07 21:18 ` Andrea Corallo
2022-08-07 11:32 ` Lynn Winebarger [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
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='CAM=F=bCaUv17=bFHppc4rsqm6REpqtvF0kK-2_QL4_92yOmJFw@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=56988@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=larsi@gnus.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).