Bug#1053761: bullseye-pu: package llvm-toolchain-16/16.0.6-15~deb11u1

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

Control: tags -1 + confirmed

On Tue, 2023-10-10 at 12:21 -0400, Andres Salomon wrote:
> Chromium newest version FTBFS on bullseye with clang-13, but works
> fine with clang-16.
> 
> [ Reason ]
> Chromium 118 (which will likely be released as stable today, and
> probably with CVEs) fails to build on bullseye's clang-13 with an
> issue that I can't figure out. I've got plenty of clang-13
> workarounds in chromium already, but this most recent issue is in a
> large (tens of thousands of lines long), complex autogenerated c++
> file. The file is generated exactly the same on bookworm & bullseye,
> but fails on bullseye's clang-13 while succeeding on bookworm's
> clang-14. I'm stuck at this point, and having clang-16 in bullseye
> would allow us to easily continue chromium's bullseye-security
> support. It will also allow us to drop a bunch of crufty workaround
> patches.
> 
> [ Impact ]
> There's no impact for users, as packages in stable must explicitly
> choose to build against clang-16.
> 

Please go ahead.

I'm not keen on the disconnect with landing a new version in bullseye
before bookworm so, while I understand why bullseye preparation has
been given priority, getting bookworm updated (via a separate request)
would be appreciated.

Regards,

Adam