Bug#1084954: Fwd: llvm-toolchain-*: assembly code seems to depend on build cpu capabilities

[Paul Gevers]

Hi h01ger,

On 29-01-2025 19:19, Holger Levsen wrote:
> On Thu, Jan 09, 2025 at 10:38:54AM +0100, Paul Gevers wrote:
>> I did that for both the armel and armhf architectures (see the
>> arm32-defaults.diff patch), but this is unchecked for any other release
>> architectures, and obviously wrong for some architectures.
>>
>> Please could you run (at least on amd64)
>> /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --help
>> and look for the last lines like
>>
>> Subdirectories of glibc-hwcaps directories, in priority order:
>>    x86-64-v4 (supported, searched)
>>    x86-64-v3 (supported, searched)
>>    x86-64-v2 (supported, searched)
>>
>> on the machines where you saw that?
> 
> shall I (still) run this on all our amd64 build nodes (which are 4) and just
> attach the results to this bug report?


I assume it is still valid to do this. At least without information this 
bug might remain RC and I understand is hardly actionable. I guess you 
only need to inspect the two nodes that were used for one of the failing 
llvm-toolchain-18|19 runs e.g. ionos1-amd64 vs ionos15-amd64

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-llvm-team/attachments/20250406/6ce780a3/attachment.sig>