From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: 48591@debbugs.gnu.org
Cc: kiasoc5 <kiasoc5@disroot.org>,
Christopher Howard <christopher@librehacker.com>,
zimoun <zimon.toutoune@gmail.com>,
raingloom <raingloom@riseup.net>,
Leo Famulari <leo@famulari.name>
Subject: bug#48591: ugrep: reproducibility issues
Date: Thu, 24 Oct 2024 12:04:45 -0700 [thread overview]
Message-ID: <87y12d8gqa.fsf@wireframe> (raw)
In-Reply-To: <f88e8548-3555-372a-9043-2c03484b64be@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On 2023-01-16, kiasoc5 wrote:
> Is this bug fixed yet?
>
> If not, seeing that this issue was motivated by an illegal instruction,
> we can use compile flags to disable SSE and other platform-dependent
> optimizations and investigate further.
>
> WDYT?
>
> https://github.com/Genivia/ugrep#other-platforms-step-3-build
--disable-sse2 disable SSE2 and AVX optimizations
--disable-avx2 disable AVX2 and AVX512BW optimizations, but compile with SSE2 when supported
--disable-neon disable ARM NEON/AArch64 optimizations
Seems like --disable-sse2 on x86_64 and x86 (32-bit) and --disable-neon
(armhf, maybe aarch64) would be needed to make the build independent of
which cpu it runs on.
FWIW, debian disables several of these (--disable-sse2 and
--disable-neon), although also passes --disable-avx which is not mentioned in
the upstream documentation, although is present in configure.ac...
https://salsa.debian.org/debian/ugrep/-/blob/7e2383dfaec23d58587f53c31ce46ef884513975/debian/rules#L5-13
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2024-10-24 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 20:19 bug#48591: ugrep: illegal instruction Christopher Howard
2021-05-22 22:46 ` Christopher Howard
2021-05-24 17:22 ` Leo Famulari
2021-06-30 21:41 ` raingloom
2021-07-02 2:23 ` Leo Famulari
2021-07-02 11:24 ` zimoun
2023-01-17 1:37 ` bug#48591: ugrep: reproducibility issues kiasoc5 via Bug reports for GNU Guix
2024-10-24 19:04 ` Vagrant Cascadian [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y12d8gqa.fsf@wireframe \
--to=vagrant@reproducible-builds.org \
--cc=48591@debbugs.gnu.org \
--cc=christopher@librehacker.com \
--cc=kiasoc5@disroot.org \
--cc=leo@famulari.name \
--cc=raingloom@riseup.net \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).