Your message dated Mon, 26 Oct 2026 09:22:28 +0000
with message-id <[email protected]>
and subject line Bug#1116637: fixed in llvm-toolchain-snapshot
1:24~++20261025103442+7e3c57157096-1~exp1
has caused the Debian Bug report #1116637,
regarding llvm-toolchain-snapshot: unsoundness/miscompilations on i386
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1116637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116637
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rustc
Version: 1.84.0+dfsg1-1
Severity: serious
Tags: upstream
Justification: Policy 2.2.1
X-Debbugs-Cc: [email protected], [email protected]
Filing this bug to have a record in BTS - I'll file a separate one for
release.debian.org about the broader baseline question.
This issue came up back in November on debian-devel/-release:
https://lists.debian.org/debian-release/2024/11/msg00443.html
My original mail, partially wrongly summarizing the issue.
https://lists.debian.org/debian-release/2024/11/msg00445.html
My reponse linking to more upstream details, including why downgrading to i586
in LLVM/rustc doesn't work.
It boils down to the following:
- Debian's i386 baseline is currently 32-bit x86 without MMX or SSE (i686)
- Debian's LLVM and rustc packages accordingly patch their i686 targets to
remove SSE support, which would be part of that target's baseline upstream
otherwise [0,1]
- Upstream LLVM and rustc consider this combination unsound and unfixable (for
IMHO valid reasons) because it can cause subtle miscompilations leading to
runtime crashes, in addition to the (usual, expected) different semantics of
x87 and SSE2 floating point implementations [2,3]
I see the following options:
A) bump i386 baseline for Trixie to match LLVM/rustc's upstream i686 target,
i.e. Pentium 4 *with* MMX and SSE2 (separate RT bug will be filed shortly)
B) RC-ignore this bug and implications for Trixie, bump baseline for Trixie+1
C) remove LLVM and rustc and all their transitive rdeps (this includes Firefox
and Chromium, most major Desktop environments, sequoia, and probably a bit
more) on i386 from Trixie, further reducing the usefulness of this arch
Personally (with my rustc maintainer hat on) I have a strong preference for A).
Please keep responses on details of A) to the corresponding release.debian.org
bug!
Fabian
0:
https://salsa.debian.org/rust-team/rust/-/blob/debian/sid/debian/patches/behaviour/d-rustc-i686-baseline.patch?ref_type=heads
1:
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/blob/19/debian/patches/clang-baseline-fix-i386.patch
2: https://github.com/rust-lang/compiler-team/issues/808
3: https://github.com/rust-lang/rust/issues/114479#issuecomment-2072052116
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-snapshot
Source-Version: 1:24~++20261025103442+7e3c57157096-1~exp1
Done: Sylvestre Ledru <[email protected]>
We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-snapshot, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sylvestre Ledru <[email protected]> (supplier of updated
llvm-toolchain-snapshot package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 19 Oct 2026 17:47:54 +0200
Source: llvm-toolchain-snapshot
Architecture: source
Version: 1:24~++20261025103442+7e3c57157096-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: LLVM Packaging Team <[email protected]>
Changed-By: Sylvestre Ledru <[email protected]>
Closes: 1116637
Changes:
llvm-toolchain-snapshot (1:24~++20261025103442+7e3c57157096-1~exp1)
experimental; urgency=medium
.
* Remove OCaml support (and the libllvm-X.Y-ocaml-dev package). Thanks
to Stephane Glondu for the fix
* Enable sse2 back on i386 (Closes: #1116637).
It is now the same as upstream. Thanks to Simon McVittie
* Ship the clang-doc assets (share/clang-doc/) in clang-tools-X.Y with
the clang-doc binary instead of clang-X.Y-doc, so that the HTML output
works (see #1142559)
* Make the source-path entries of /usr/lib/<triplet>/libc++.modules.json
absolute, the relative ones only worked from /usr/lib/llvm-X.Y/lib
(see #1142558)
* Fix the remove_rpath macro in d/rules: it over-escaped '$' so it never
stripped anything. clang-query kept its build-dir RUNPATH with a
trailing ':' which made ld.so look in the current directory (CWE-427).
(see #1142995)
.
[ Changes merged from llvm-toolchain-23 ]
* libmlir-X.Y-dev: drop the Conflicts against the libmlir-x.y-dev virtual
package, everything is installed under /usr/lib/llvm-X.Y so it is
co-installable with the other versions (see #1142996)
* d/debian-llvm-testsuite.bats: add two tests covering the location of
the MLIR libraries in /usr/lib/<triplet> and the co-installability
(see #1142996)
* Fix the FTBFS with doxygen 1.17: it does not generate jquery.js anymore,
only replace it by the symlink to libjs-jquery when it exists.
(see #1151646)
* libc++-X.Y-dev-wasm32, libc++abi-X.Y-dev-wasm32: also build and ship an
exception-enabled variant of libc++, libc++abi and libunwind, in
/usr/lib/wasm32-wasi/eh, used by clang with -fwasm-exceptions. Built
like wasi-sdk does (exnref, so -mllvm -wasm-use-legacy-eh=false, and
-lunwind needed at link time). The headers are identical, so shared.
The non-exception variant stays in the existing location.
d/p/wasm/wasm-sysroot-usr.diff: keep the eh/noeh include directory
lookup added upstream.
d/p/wasm/libunwind-wasm-no-declspec.diff: fix the libunwind build for
wasm (upstream PR 168449, also used by wasi-sdk).
Add an autopkgtest. (see #1149144)
* Don't install a default lldb config file anymore: a versioned one does
not make much sense and an unversioned one conflicts between versions
(see #1147981). Thanks to Norbert Lange
* Fix i386 FTBFS: build LLVMSupport with SSE2 when _Float16 requires it
(d/p/llvm-support-force-sse2-float16.diff), and disable the precompiled
headers on x86-32 so that the rest of LLVM does not reuse the +sse2 one.
* d/debian-llvm-testsuite.bats: use -analyzer-constraints=unsupported-z3,
upstream renamed the z3 constraint manager backend in LLVM 23
(see #1145851)
Checksums-Sha1:
f199bd19167dfd3a160c9411f351a50cae513b2d 15577
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096-1~exp1.dsc
2a3df308391e10b0aba4ddd9352089b067d21c6b 253667072
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096.orig.tar.xz
74e76e3280b52da7726326f734a680d8b47f6934 194192
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096-1~exp1.debian.tar.xz
cff4eb58b7886b45627e2567d1a8512f0824b594 46447
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096-1~exp1_amd64.buildinfo
Checksums-Sha256:
618e4d4cb8c2e034fef7be0180fe3e9eba262f8b75ec0c202ec52e3e7b5621c2 15577
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096-1~exp1.dsc
243b027d906fc8cf43a19b75529871bceb8a465448a74b46f247c8aa58569ee7 253667072
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096.orig.tar.xz
ac8d9bcf5b9e6be826ac1aeb5cbc26e1e61fb9bff34bdf2291fd7dfe8569acbe 194192
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096-1~exp1.debian.tar.xz
2d35a75853e8df5f4e499a5070d371f03c37b0063fb5d07758b6a9b9439bc2e3 46447
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096-1~exp1_amd64.buildinfo
Files:
59f16abb8e9e944ab0be19c8860315e0 15577 devel optional
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096-1~exp1.dsc
03e88e6fa96b53394d961850c776dfce 253667072 devel optional
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096.orig.tar.xz
134660879fd2b6494800c9c07896fdea 194192 devel optional
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096-1~exp1.debian.tar.xz
ebb0b07119772f6f14cc9c9dc906aaa5 46447 devel optional
llvm-toolchain-snapshot_24~++20261025103442+7e3c57157096-1~exp1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmrfFfIACgkQfmUo2nUv
G+G3SRAAjbXAHYEaPBpvaI5PLNrXwNRAAOW+KhLqLGEIEsTBZCyWblnNAF+8+QEB
kZZOTEbKEoJQf4UKqBKhIXL+JQsP0jzP/5jyW4jsvn9gA6WmAtU6EZApZHXT9HDp
D+Dl9V9W8RQeBqK8gTQJflv1J/b+aqe4NPH7R81Onk1iSCc2lhz7Xb41eynvhGaS
QlqyxYWqnZeCTq+NE/aPGMX8sA+HNvh0ZZkoGDOX9f/aTE3pS/wH7tB9WuH36PWJ
blJCUNvRWUcfhniTgvQtMngN/KGao67pXjEBxJ74hsectb4ODaY48bbcf05K9ngP
J9DO3l9Zo5Mqy+8ohOWgF2euDiSgDEGWm4SFdnVs1tU36wGlXLYrZo1Ex8NLdD8B
9Tp6lQs2sVnhYSPue6fvgemuFaP2TVF6Z/tk6GVBn7p4Jqvb2aL2jW8tv7ChRF5x
GdUAnRAFeiA4Uu/7Trf53sVh98kn2iTY8iPZiaWQVlFs8UeRFT/xet/jIMbsu6F2
1GaiWP24B1gXoh3KyhxP6lwxOjLIg4ZAsMB8SH2BncZO/7bcYrPTNN2MoO4ucmPS
CnnUO0nB0pp3OLA5ZrQ4GBvADxYhNj9bo+Kgz5vS04KTq8l25phOxJn5KWyjyACj
x6uZygj1qM2g3ChbVa1A8t1iouTct7V0LGwMs0Gr24Y+FRLJmZw=
=toEb
-----END PGP SIGNATURE-----
pgpljKbHFK4uD.pgp
Description: PGP signature
--- End Message ---
