From: iyzsong@member.fsf.org (宋文武)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: zita-convolver: Drop the '-march=native' optimization.
Date: Thu, 07 Jan 2016 11:58:34 +0800 [thread overview]
Message-ID: <87y4c2qbv9.fsf@member.fsf.org> (raw)
In-Reply-To: <874meq5s30.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 06 Jan 2016 22:13:55 +0100")
Ricardo Wurmus <rekado@elephly.net> writes:
>> + (snippet
>> + ;; Don't optimize for a specific processor architecture.
>> + '(substitute* "libs/Makefile"
>> + (("^CXXFLAGS \\+= -march=native") "")))
>> + (modules '((guix build utils)))
>
> Is this to avoid that packages are optimised for the CPU of the build
> slave?
Yes, using that from hydra will crash guitarix for me.
Same as: <https://bugs.archlinux.org/task/36248>.
> If so, could we instead pass different optimisation flags for
> different architectures? For a convolver I’d prefer to have *some*
> optimisation, even if it’s just the greatest common divisor.
I don't familiar with optimization flags, but according to:
<https://wiki.gentoo.org/wiki/GCC_optimization#Optimizing>
I think '-march=native' should be dropped definitely, it enable all
the CPU specified instruction set when building on the slave.
And it's not clear to me what *some* flags are, suppose we don't want
any CPU specified (-msse3, -msse4, etc.) thing.
next prev parent reply other threads:[~2016-01-07 3:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 15:48 [PATCH 2/2] gnu: zita-convolver: Drop the '-march=native' optimization 宋文武
2016-01-06 21:13 ` Ricardo Wurmus
2016-01-07 3:58 ` 宋文武 [this message]
2016-01-07 8:37 ` Ricardo Wurmus
2016-01-07 13:20 ` Ludovic Courtès
2016-01-07 14:53 ` 宋文武
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=87y4c2qbv9.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).