[From nobody Wed Jul  8 17:35:05 2026
Received: (at submit) by bugs.debian.org; 20 Feb 2026 08:31:34 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-109.1 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
 DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,
 FROMDEVELOPER,SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY,
 USER_IN_DKIM_WELCOMELIST,XMAILER_REPORTBUG autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 10; hammy, 144; neutral, 30; spammy,
 0. spammytokens:
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: &lt;dparsons@debian.org&gt;
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:42178)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;dparsons@debian.org&gt;) id 1vtLvC-007ZlZ-1d
 for submit@bugs.debian.org; Fri, 20 Feb 2026 08:31:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Date:Message-ID:Subject:To:From:
 Content-Transfer-Encoding:MIME-Version:Content-Type:Reply-To:Cc:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=PShsT+obCePQW6woQ3FBEX311kN/M18eUrMPxA3XiiM=; b=R9xdXhn93A7FKJtNXc4CdduI8U
 Y8rC5k3wSRE2ryvKOfkAZpJL51PmQksL1qLT7xa4VmJ1MS1uR1wo25bW3XDDn+YgMJzty4QyJmEYv
 tQ76DbodDn7MEIPlMs+lo2F/RXbiFM9FD5uOvZdc9/PESzj2eIMk7Y3qJfNm2zM2xV8g/szyNkLeU
 6UElfNNetw8HViPoL+itI3FHMVRlvVtTKiKmMPUXNuGZsaVOfoRLJiZ8qD7csYxQadPl/Wvr3bEpo
 D8Emt2mY8lRSzRskem+BWlJWSDoyOkfY7qN6o/AF4PQ2pjlnU3VMcXyWSOA/ij3jiByZbWy3ZRqW/
 PO8QJr1g==;
Received: from authenticated user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.94.2) (envelope-from &lt;dparsons@debian.org&gt;)
 id 1vtLvB-006War-HB; Fri, 20 Feb 2026 08:31:32 +0000
Received: from drew by sandy with local (Exim 4.99.1)
 (envelope-from &lt;dparsons@debian.org&gt;) id 1vtLv8-0000000EmiT-1ZUA;
 Fri, 20 Feb 2026 09:31:30 +0100
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Drew Parsons &lt;dparsons@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: xsimd: drop arch-specific armhf build flags
Message-ID: &lt;177157629033.3496668.8211200044126729496.reportbug@sandy&gt;
X-Mailer: reportbug 13.2.0
Date: Fri, 20 Feb 2026 09:31:30 +0100
X-Debian-User: dparsons
Delivered-To: submit@bugs.debian.org

Source: xsimd
Version: 14.0.0-5
Severity: normal
X-Debbugs-Cc: debian-arm@lists.debian.org
User: debian-arm@lists.debian.org
Usertags: armhf
Control: forwarded -1 https://github.com/xtensor-stack/xsimd/issues/1260

Bug#1128257 requested we drop the arch-specific build flags for armhf.
But we found they are still needed to manage failure with NEON code on
32-bit ARM, and instead updated them to -march=armv7-a+fp

However, the principle of not applying arch-specific build flags is
still reasonable in general. We should drop them if we can.

This requires help upstream to resolve the SIGABRT in 
  [batch]&lt;xsimd::batch&lt;unsigned char&gt;&gt;
on 32-bit ARM systems that claim neon support
(i.e. on armv8l, which is Aarch64 hardware but used by debian to provide armhf environments).

This is upstream issue #1260.
]