Bug#1104337: marked as done (llvm-toolchain-20: unsoundness/miscompilations on i386)

Tue, 18 Aug 2026 09:39:21 -0700 

Your message dated Tue, 18 Aug 2026 18:37:48 +0200
with message-id <[email protected]>
and subject line [[email protected]: Bug#1116216 closed by Debian FTP 
Masters <[email protected]> (Bug#1116216: Removed package(s) from 
experimental)]
has caused the Debian Bug report #1104337,
regarding llvm-toolchain-20: 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.)


-- 
1104337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104337
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 --- 
Closing bugs reported against llvm-toolchain-20 now that it got removed 
from the archive.

----- Message transféré de Debian Bug Tracking System <[email protected]> 
-----

From: Debian Bug Tracking System <[email protected]>
To: Sylvestre Ledru <[email protected]>
Reply-To: [email protected]
X-Mailer: MIME-tools 5.510 (Entity 5.510)
Date: Tue, 14 Jul 2026 09:33:02 +0000
Subject: Bug#1116216 closed by Debian FTP Masters 
<[email protected]> (Bug#1116216: Removed package(s) from 
experimental)
Message-ID: 
<handler.1116216.d1116216.17840214462041426.notifd...@bugs.debian.org>

This is an automatic notification regarding your Bug report
which was filed against the ftp.debian.org package:

#1116216: RM: llvm-toolchain-20/experimental -- ROM; Won't be in unstable

It has been closed by Debian FTP Masters <[email protected]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Debian FTP Masters 
<[email protected]> by
replying to this email.


-- 
1116216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116216
Debian Bug Tracking System
Contact [email protected] with problems

From: Debian FTP Masters <[email protected]>
To: [email protected]
Cc: [email protected]
X-Spam-Status: No, score=-107.1 required=4.0 tests=BAYES_00,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HAS_BUG_NUMBER,
 RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS,USER_IN_DKIM_WELCOMELIST
 autolearn=ham autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
Date: Tue, 14 Jul 2026 09:30:42 +0000
Subject: Bug#1116216: Removed package(s) from experimental
Message-Id: <[email protected]>

We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:

   bolt-20 | 1:20.1.8-1+b4 | amd64, arm64
  clang-20 | 1:20.1.8-1~exp1 | s390x
  clang-20 | 1:20.1.8-1+b2 | riscv64
  clang-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
clang-20-doc | 1:20.1.8-1~exp1 | all
clang-20-doc | 1:20.1.8-1 | all
clang-20-examples | 1:20.1.8-1~exp1 | all
clang-20-examples | 1:20.1.8-1 | all
clang-format-20 | 1:20.1.8-1~exp1 | s390x
clang-format-20 | 1:20.1.8-1+b2 | riscv64
clang-format-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
clang-tidy-20 | 1:20.1.8-1~exp1 | s390x
clang-tidy-20 | 1:20.1.8-1+b2 | riscv64
clang-tidy-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
clang-tools-20 | 1:20.1.8-1~exp1 | s390x
clang-tools-20 | 1:20.1.8-1+b2 | riscv64
clang-tools-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
 clangd-20 | 1:20.1.8-1~exp1 | s390x
 clangd-20 | 1:20.1.8-1+b2 | riscv64
 clangd-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
  flang-20 | 1:20.1.8-1+b2 | riscv64
  flang-20 | 1:20.1.8-1+b4 | amd64, arm64, loong64, ppc64el
libbolt-20-dev | 1:20.1.8-1+b4 | amd64, arm64
libc++-20-dev | 1:20.1.8-1~exp1 | s390x
libc++-20-dev | 1:20.1.8-1+b2 | riscv64
libc++-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
libc++-20-dev-wasm32 | 1:20.1.8-1~exp1 | all
libc++-20-dev-wasm32 | 1:20.1.8-1 | all
libc++abi-20-dev | 1:20.1.8-1~exp1 | s390x
libc++abi-20-dev | 1:20.1.8-1+b2 | riscv64
libc++abi-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
libc++abi-20-dev-wasm32 | 1:20.1.8-1~exp1 | all
libc++abi-20-dev-wasm32 | 1:20.1.8-1 | all
libclang-20-dev | 1:20.1.8-1~exp1 | s390x
libclang-20-dev | 1:20.1.8-1+b2 | riscv64
libclang-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
libclang-common-20-dev | 1:20.1.8-1~exp1 | s390x
libclang-common-20-dev | 1:20.1.8-1+b2 | riscv64
libclang-common-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, 
ppc64el
libclang-cpp20 | 1:20.1.8-1~exp1 | s390x
libclang-cpp20 | 1:20.1.8-1+b2 | riscv64
libclang-cpp20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
libclang-cpp20-dev | 1:20.1.8-1~exp1 | s390x
libclang-cpp20-dev | 1:20.1.8-1+b2 | riscv64
libclang-cpp20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
libclang-rt-20-dev | 1:20.1.8-1~exp1 | s390x
libclang-rt-20-dev | 1:20.1.8-1+b2 | riscv64
libclang-rt-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
libclang-rt-20-dev-wasm32 | 1:20.1.8-1~exp1 | all
libclang-rt-20-dev-wasm32 | 1:20.1.8-1 | all
libclang-rt-20-dev-wasm64 | 1:20.1.8-1~exp1 | all
libclang-rt-20-dev-wasm64 | 1:20.1.8-1 | all
libclang-rt-20-dev-win | 1:20.1.8-1 | all
libclang1-20 | 1:20.1.8-1~exp1 | s390x
libclang1-20 | 1:20.1.8-1+b2 | riscv64
libclang1-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
 libclc-20 | 1:20.1.8-1~exp1 | all
 libclc-20 | 1:20.1.8-1 | all
libclc-20-dev | 1:20.1.8-1~exp1 | all
libclc-20-dev | 1:20.1.8-1 | all
libflang-20-dev | 1:20.1.8-1+b2 | riscv64
libflang-20-dev | 1:20.1.8-1+b4 | amd64, arm64, loong64, ppc64el
libfuzzer-20-dev | 1:20.1.8-1~exp1 | s390x
libfuzzer-20-dev | 1:20.1.8-1+b2 | riscv64
libfuzzer-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
 liblld-20 | 1:20.1.8-1~exp1 | s390x
 liblld-20 | 1:20.1.8-1+b2 | riscv64
 liblld-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
liblld-20-dev | 1:20.1.8-1~exp1 | s390x
liblld-20-dev | 1:20.1.8-1+b2 | riscv64
liblld-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
liblldb-20 | 1:20.1.8-1~exp1 | s390x
liblldb-20 | 1:20.1.8-1+b2 | riscv64
liblldb-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
liblldb-20-dev | 1:20.1.8-1~exp1 | s390x
liblldb-20-dev | 1:20.1.8-1+b2 | riscv64
liblldb-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
libllvm-20-ocaml-dev | 1:20.1.8-1~exp1 | s390x
libllvm-20-ocaml-dev | 1:20.1.8-1+b2 | riscv64
libllvm-20-ocaml-dev | 1:20.1.8-1+b4 | amd64, arm64, ppc64el
 libllvm20 | 1:20.1.8-1~exp1 | s390x
 libllvm20 | 1:20.1.8-1+b2 | riscv64
 libllvm20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
libllvmlibc-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf
libmlir-20 | 1:20.1.8-1~exp1 | s390x
libmlir-20 | 1:20.1.8-1+b2 | riscv64
libmlir-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
libmlir-20-dev | 1:20.1.8-1~exp1 | s390x
libmlir-20-dev | 1:20.1.8-1+b2 | riscv64
libmlir-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
liboffload-20 | 1:20.1.8-1+b4 | amd64, arm64, loong64, ppc64el
liboffload-20-dev | 1:20.1.8-1+b4 | amd64, arm64, loong64, ppc64el
libomp-20-dev | 1:20.1.8-1+b2 | riscv64
libomp-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, loong64, ppc64el
libomp-20-doc | 1:20.1.8-1~exp1 | all
libomp-20-doc | 1:20.1.8-1 | all
libpolly-20-dev | 1:20.1.8-1~exp1 | s390x
libpolly-20-dev | 1:20.1.8-1+b2 | riscv64
libpolly-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
libunwind-20-dev | 1:20.1.8-1+b2 | riscv64
libunwind-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
    lld-20 | 1:20.1.8-1~exp1 | s390x
    lld-20 | 1:20.1.8-1+b2 | riscv64
    lld-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
   lldb-20 | 1:20.1.8-1~exp1 | s390x
   lldb-20 | 1:20.1.8-1+b2 | riscv64
   lldb-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
   llvm-20 | 1:20.1.8-1~exp1 | s390x
   llvm-20 | 1:20.1.8-1+b2 | riscv64
   llvm-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
llvm-20-dev | 1:20.1.8-1~exp1 | s390x
llvm-20-dev | 1:20.1.8-1+b2 | riscv64
llvm-20-dev | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
llvm-20-doc | 1:20.1.8-1~exp1 | all
llvm-20-doc | 1:20.1.8-1 | all
llvm-20-examples | 1:20.1.8-1~exp1 | all
llvm-20-examples | 1:20.1.8-1 | all
llvm-20-linker-tools | 1:20.1.8-1~exp1 | s390x
llvm-20-linker-tools | 1:20.1.8-1+b2 | riscv64
llvm-20-linker-tools | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, 
ppc64el
llvm-20-runtime | 1:20.1.8-1~exp1 | s390x
llvm-20-runtime | 1:20.1.8-1+b2 | riscv64
llvm-20-runtime | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
llvm-20-tools | 1:20.1.8-1~exp1 | s390x
llvm-20-tools | 1:20.1.8-1+b2 | riscv64
llvm-20-tools | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
llvm-toolchain-20 | 1:20.1.8-1~exp1 | source
llvm-toolchain-20 | 1:20.1.8-1 | source
mlir-20-tools | 1:20.1.8-1~exp1 | s390x
mlir-20-tools | 1:20.1.8-1+b2 | riscv64
mlir-20-tools | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
python3-clang-20 | 1:20.1.8-1~exp1 | s390x
python3-clang-20 | 1:20.1.8-1+b2 | riscv64
python3-clang-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el
python3-lldb-20 | 1:20.1.8-1~exp1 | s390x
python3-lldb-20 | 1:20.1.8-1+b2 | riscv64
python3-lldb-20 | 1:20.1.8-1+b4 | amd64, arm64, armhf, i386, loong64, ppc64el

------------------- Reason -------------------
ROM; Won't be in unstable
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected].

The full log for this bug can be viewed at https://bugs.debian.org/1116216

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

From: Sylvestre Ledru <[email protected]>
To: Debian Bug Tracking System <[email protected]>
X-Mailer: reportbug 13.2.0
X-Spam-Status: No, score=-31.0 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_CONTROL_AFFECTS,BODY_INCLUDES_PACKAGE,FROMDEVELOPER,
 HAS_PACKAGE,RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,
 RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED,
 SPF_HELO_NONE,SPF_NONE,XMAILER_REPORTBUG autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
Date: Wed, 24 Sep 2025 13:16:18 +0200
Subject: RM: llvm-toolchain-20/experimental -- ROM; Won't be in unstable
Message-ID: 
<175871257897.3751907.3638191059166209781.report...@burias.ecranbleu.org>

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:llvm-toolchain-20
User: [email protected]
Usertags: remove


Hello,

Please remove llvm-toolchain-20 from experimental
To make our life easier, i won't be uploading in unstable.
We have now 21 and 19 if needed.

thanks
Sylvestre


----- Fin du message transféré -----

--- End Message ---

Reply via email to