From: Mark H Weaver <mhw@netris.org>
To: "Pierre Neidhardt" <mail@ambrevar.xyz>,
"Ludovic Courtès" <ludo@gnu.org>,
"Guillaume Le Vaillant" <glv@posteo.net>
Cc: 33848@debbugs.gnu.org
Subject: bug#33848: Store references in SBCL-compiled code are "invisible"
Date: Thu, 01 Apr 2021 02:03:06 -0400 [thread overview]
Message-ID: <87czvebky2.fsf@netris.org> (raw)
In-Reply-To: <87im57b8u7.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> - The main recommendation for an easy fix without updating the scanner
> is that we tweaked our build system to dump the store reference to a
> separate ASCII file.
Sounds good. I made a similar proposal in Dec 2018, earlier in this
thread <https://bugs.gnu.org/33848#31>. I wrote:
If you don't want to change the daemon, it could be worked around in our
build-side code as follows: we could add a new phase to certain build
systems (or possibly gnu-build-system) that scans each output for
UTF-16/32 encoded store references that are never referenced in UTF-8.
If such references exist, a file with an unobtrusive name would be added
to that output containing those references encoded in UTF-8. This would
enable our daemon's existing reference scanner to find all of the
references.
Our grafting code would then need to be extended to recognize and
transform store references encoded in UTF-16/32 as well as UTF-8.
Mark
next prev parent reply other threads:[~2021-04-01 6:06 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 14:19 bug#33848: Store references in SBCL-compiled code are "invisible" Ludovic Courtès
2018-12-23 15:05 ` Pierre Neidhardt
2018-12-24 14:57 ` Ludovic Courtès
2018-12-23 16:45 ` Mark H Weaver
2018-12-23 17:32 ` Ludovic Courtès
2018-12-23 22:01 ` Pierre Neidhardt
2018-12-24 15:06 ` Ludovic Courtès
2018-12-24 17:08 ` Pierre Neidhardt
2018-12-26 16:07 ` Ludovic Courtès
2018-12-24 18:12 ` Mark H Weaver
2018-12-24 23:58 ` Pierre Neidhardt
2018-12-26 16:14 ` Ludovic Courtès
2018-12-27 10:37 ` Pierre Neidhardt
2018-12-27 14:03 ` Mark H Weaver
2018-12-27 14:45 ` Ludovic Courtès
2018-12-27 15:02 ` Pierre Neidhardt
2018-12-27 16:15 ` Pierre Neidhardt
2018-12-27 17:03 ` Ludovic Courtès
2018-12-27 18:57 ` Pierre Neidhardt
2018-12-27 21:54 ` Ludovic Courtès
2018-12-27 22:05 ` Pierre Neidhardt
2018-12-27 22:59 ` Ludovic Courtès
2018-12-28 7:47 ` Pierre Neidhardt
2021-03-30 10:15 ` Pierre Neidhardt
2021-03-30 20:09 ` Ludovic Courtès
2021-03-31 7:10 ` Pierre Neidhardt
2021-03-31 16:12 ` Pierre Neidhardt
2021-03-31 20:42 ` Ludovic Courtès
2021-03-31 20:57 ` Pierre Neidhardt
2021-04-01 17:23 ` Mark H Weaver
2021-04-02 15:13 ` Ludovic Courtès
2021-04-01 6:03 ` Mark H Weaver [this message]
2021-04-01 7:13 ` Pierre Neidhardt
2021-04-01 7:57 ` Ludovic Courtès
2021-04-01 8:48 ` Pierre Neidhardt
2021-04-01 9:07 ` Guillaume Le Vaillant
2021-04-01 9:13 ` Pierre Neidhardt
2021-04-01 9:52 ` Guillaume Le Vaillant
2021-04-01 10:06 ` Pierre Neidhardt
2021-04-01 10:07 ` Pierre Neidhardt
2021-04-01 15:24 ` Ludovic Courtès
2021-04-01 17:33 ` Mark H Weaver
2021-04-02 22:46 ` Mark H Weaver
2021-04-03 6:51 ` Pierre Neidhardt
2021-04-03 20:10 ` Mark H Weaver
2021-04-05 19:45 ` Ludovic Courtès
2021-04-05 23:04 ` Mark H Weaver
2021-04-06 8:16 ` Ludovic Courtès
2021-04-06 8:23 ` Pierre Neidhardt
2021-04-30 20:03 ` Mark H Weaver
2021-05-01 9:22 ` Pierre Neidhardt
2021-05-11 8:46 ` Ludovic Courtès
2021-04-06 17:23 ` Leo Famulari
2021-04-06 23:21 ` Mark H Weaver
2021-04-06 11:19 ` Mark H Weaver
2021-04-08 10:13 ` Ludovic Courtès
2021-04-13 20:06 ` Mark H Weaver
2021-04-14 10:55 ` Ludovic Courtès
2021-04-14 22:37 ` Leo Famulari
2021-04-15 7:26 ` Mark H Weaver
2021-04-16 9:44 ` Pierre Neidhardt
2018-12-27 13:52 ` Danny Milosavljevic
2018-12-27 14:29 ` Mark H Weaver
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czvebky2.fsf@netris.org \
--to=mhw@netris.org \
--cc=33848@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=ludo@gnu.org \
--cc=mail@ambrevar.xyz \
/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/guix.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).