From: Andrea Corallo <akrl@sdf.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 51104@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Andrea Corallo <andrea_corallo@yahoo.it>
Subject: bug#51104: comp-tests.elc messes up after reconfiguring for different machine
Date: Tue, 13 Sep 2022 14:09:04 +0000 [thread overview]
Message-ID: <xjfa673cqnz.fsf@ma.sdf.org> (raw)
In-Reply-To: <87bkrj4izy.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 13 Sep 2022 13:21:53 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>>> Andrea, do you see any way to fix this test for this 32-bit/64-bit
>>>> scenarion?
>>
>> Not Andrea, but IIUC the patch below might do the trick.
>> Can someone confirm?
>
> I think that looks better than disabling byte-compilation (because the
> comp tests are already slow enough 😀).
Comp tests are unfortunatelly slow not because comp-tests.el is slow but
because of the compiler itself is not fast :/
Anyway Stefan fix is certanly nicer, I feel sorry for not having had the
time to look into it myself.
Thanks!
Andrea
prev parent reply other threads:[~2022-09-13 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 22:59 bug#51104: comp-tests.elc messes up after reconfiguring for different machine Paul Eggert
2022-09-12 11:15 ` Lars Ingebrigtsen
2022-09-12 11:43 ` Eli Zaretskii
2022-09-12 15:30 ` Andrea Corallo
2022-09-12 17:54 ` Paul Eggert via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 19:34 ` Andrea Corallo
2022-09-12 20:34 ` Paul Eggert via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 21:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 11:21 ` Lars Ingebrigtsen
2022-09-13 13:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 14:09 ` 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
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=xjfa673cqnz.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=51104@debbugs.gnu.org \
--cc=andrea_corallo@yahoo.it \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.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).