From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: bug#33848: Store references in SBCL-compiled code are "invisible" Date: Sun, 23 Dec 2018 16:05:57 +0100 Message-ID: <87a7kwjnai.fsf@ambrevar.xyz> References: <87r2e8jpfx.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48676) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gb5LN-0003Yj-LA for bug-guix@gnu.org; Sun, 23 Dec 2018 10:07:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gb5LK-0002iQ-Dx for bug-guix@gnu.org; Sun, 23 Dec 2018 10:07:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:57865) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gb5LK-0002iC-Ai for bug-guix@gnu.org; Sun, 23 Dec 2018 10:07:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gb5LK-0002yu-1S for bug-guix@gnu.org; Sun, 23 Dec 2018 10:07:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48343) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gb5KP-0003W7-Qs for bug-guix@gnu.org; Sun, 23 Dec 2018 10:06:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gb5KM-0001YX-I2 for bug-guix@gnu.org; Sun, 23 Dec 2018 10:06:05 -0500 In-reply-to: <87r2e8jpfx.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 33848@debbugs.gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Thanks for looking into this, Ludo. At first glance, I'd say that this is not a compilation option but the way strings are encoded by default. It seems that multibyte encoding is used a= ll over the place by a few compilers including SBCL (and CCL I think). One way I know around this (I'm by no mean a Common Lisp expert) is the flexi-streams package for re-encoding. More generally, shouldn't we make the reference scanner a bit smarter? In particular, how does it handle non-ASCII references? Maybe it would not be unreasonable to handle UTF-8 and UCS-4 for instance? =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlwfpFUACgkQm9z0l6S7 zH/rdggAnQg4EGjzFVDFFNwofXuTBydyu+uLV6FHjagMA1ijxaEPtL27NhmdWUdM oFgRKIKabQpixyDSWJhAPGPIv2JHdrqiBwNRUfaDWSKhoh8/qA654QF8NiSFCHaf JpXMcdYVGvQ92Fo9OUFls8CWeWSpaEgQcTeIeeTNLwDCid8ob5gFW8doaqxraGw6 dkLeqIOuenB7jI/7cBs4yD4e+r8V/IAY/mVvuTZ+gRFGu+StbMo01KRX2X1xOVaL L4WiaGhJHyDYqw3otCPfZduOvsOyfhSrov3HpPT6vocQ11Wb8tW7t+JipO+w1DLi FMG7JYdAN3ibsDXXncsKcSxgeszj1g== =oKMR -----END PGP SIGNATURE----- --=-=-=--