From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gerd.moellmann@gmail.com, 65455@debbugs.gnu.org
Subject: bug#65455: 30.0.50; Disassemble: error with "free-standing" native compiled function
Date: Fri, 25 Aug 2023 10:11:58 -0400 [thread overview]
Message-ID: <yp1v8d35hzl.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83a5ufnum6.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Aug 2023 16:01:53 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <acorallo@gnu.org>
>> Cc: gerd.moellmann@gmail.com, 65455@debbugs.gnu.org
>> Date: Fri, 25 Aug 2023 07:52:06 -0400
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> > None of the above sounds a good idea to me. How about a special
>> >> > disassemble-native function, which will keep the temporary file until
>> >> > after the disassembly, and then delete it? Gerd, would that be good
>> >> > enough?
>> >>
>> >> Mmmh, I'm not sure I undestand, how can disassemble-native keep the
>> >> temporary file if this was deleted just after it was compiled and
>> >> loaded?
>> >
>> > By instructing the compilation not to delete it, and then deleting it
>> > after disassembly, I guess?
>>
>> Okay but what if the file is never disassembled? What if it's
>> disassembled more than once? Isn't 3 simpler at this stage?
>
> I think we are mis-communicating. What I meant is something like this:
>
> . add a new optional argument to native-compile that would prevent
> it from deleting the .eln file
> . add a new function disassemble-native, which will call
> native-compile with this new argument, perform disassembly, and
> then delete the file
I see thanks for clarifying.
I'm not sure I like this option, reason is that I typically want to see
the disassembly of the already installed function rather than triggering
a new compilation. Any change in the environment can lead to a
different output so I think is important to inspect what was produced
when it was commanded, no?
Bests
Andrea
next prev parent reply other threads:[~2023-08-25 14:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 13:17 bug#65455: 30.0.50; Disassemble: error with "free-standing" native compiled function Gerd Möllmann
2023-08-22 13:29 ` Eli Zaretskii
2023-08-22 13:41 ` Gerd Möllmann
2023-08-22 15:39 ` Eli Zaretskii
2023-08-25 8:11 ` Andrea Corallo
2023-08-25 10:30 ` Eli Zaretskii
2023-08-25 11:43 ` Andrea Corallo
2023-08-25 11:47 ` Eli Zaretskii
2023-08-25 11:52 ` Andrea Corallo
2023-08-25 13:01 ` Eli Zaretskii
2023-08-25 14:11 ` Andrea Corallo [this message]
2023-08-25 14:56 ` Eli Zaretskii
2023-08-27 13:34 ` Andrea Corallo
2023-08-27 13:40 ` Eli Zaretskii
2023-08-27 15:41 ` Andrea Corallo
2023-08-27 14:43 ` Andrea Corallo
2023-08-27 16:21 ` Eli Zaretskii
2023-08-27 18:04 ` Andrea Corallo
2023-08-27 18:22 ` Eli Zaretskii
2023-10-26 6:53 ` Gerd Möllmann
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=yp1v8d35hzl.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=65455@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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).