From: Maxime Devos <maximedevos@telenet.be>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 54635@debbugs.gnu.org, Arun Isaac <arunisaac@systemreboot.net>
Subject: [bug#54635] [PATCH v2 5/5] gnu: Add wfmash.
Date: Thu, 31 Mar 2022 15:07:49 +0200 [thread overview]
Message-ID: <c9c69a2a0f95a78fc594d449b461c8d7118b1138.camel@telenet.be> (raw)
In-Reply-To: <YkWcDYc6j2XRinl8@3900XT>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
Efraim Flashner schreef op do 31-03-2022 om 15:18 [+0300]:
> > Arun Isaac schreef op do 31-03-2022 om 12:58 [+0530]:
> > > + (("-march=native") ""))
> >
> > This is also wrong for x86 systems because it makes the build non-
> > reproducible. Also, has upstream been informed about some of the
> > compiler flags being architecture-specific?
>
> I'm pretty sure upstream is aware of it, and the -mcx16 flag. That
> whole phase doesn't need to be non-x86_64 only, upstream prefers it
> that way to get fater results
wfmash could be written to detect CPU features at runtime and there is
also --tune. Also, upstream preferring march=native does not make the
build reproducible.
> but IMO it would be fine to move it into a snippet.
It does not have to be in a snippet, it just needs to be reproducible
(so no march=native, whether on x86 or not).
Upstream seems to be aware of the non-x86
(https://github.com/ekg/wfmash/issues/125) but they do not seem to be
aware of the problems with march=native.
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-03-31 13:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 9:19 [bug#54635] [PATCH 0/5] Add wfmash Arun Isaac
2022-03-30 9:23 ` [bug#54635] [PATCH 1/5] gnu: gsl: Force bootstrap when cross-compiling to riscv64-linux Arun Isaac
2022-03-30 9:23 ` [bug#54635] [PATCH 2/5] gnu: htslib: Add bzip2 and xz to inputs Arun Isaac
2022-03-30 9:23 ` [bug#54635] [PATCH 3/5] gnu: atomic-queue: Run tests correctly Arun Isaac
2022-03-30 9:23 ` [bug#54635] [PATCH 4/5] gnu: atomic-queue: Do not depend on boost when cross-compiling Arun Isaac
2022-03-30 11:49 ` Maxime Devos
2022-03-31 7:24 ` Arun Isaac
2022-03-30 9:23 ` [bug#54635] [PATCH 5/5] gnu: Add wfmash Arun Isaac
2022-03-30 11:33 ` [bug#54635] [PATCH 1/5] gnu: gsl: Force bootstrap when cross-compiling to riscv64-linux Maxime Devos
2022-03-31 6:14 ` Arun Isaac
2022-03-30 11:36 ` Maxime Devos
2022-03-30 11:39 ` Efraim Flashner
2022-03-31 6:33 ` Arun Isaac
2022-03-31 11:29 ` Maxime Devos
2022-03-31 12:35 ` Efraim Flashner
2022-03-31 7:28 ` [bug#54635] [PATCH v2 " Arun Isaac
2022-03-31 7:28 ` [bug#54635] [PATCH v2 2/5] gnu: htslib: Add bzip2 and xz to inputs Arun Isaac
2022-03-31 7:28 ` [bug#54635] [PATCH v2 3/5] gnu: atomic-queue: Run tests correctly Arun Isaac
2022-03-31 7:28 ` [bug#54635] [PATCH v2 4/5] gnu: atomic-queue: Do not look for boost when cross-compiling Arun Isaac
2022-03-31 7:28 ` [bug#54635] [PATCH v2 5/5] gnu: Add wfmash Arun Isaac
2022-03-31 11:34 ` Maxime Devos
2022-03-31 12:18 ` Efraim Flashner
2022-03-31 13:07 ` Maxime Devos [this message]
2022-03-31 13:09 ` Efraim Flashner
2022-03-31 13:31 ` bug#54635: " Efraim Flashner
2022-04-01 7:40 ` [bug#54635] " Arun Isaac
2022-04-01 9:39 ` Maxime Devos
2022-04-04 18:01 ` Arun Isaac
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c9c69a2a0f95a78fc594d449b461c8d7118b1138.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54635@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=efraim@flashner.co.il \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.