From: Mark H Weaver <mhw@netris.org>
To: Eric Bavier <bavier@cray.com>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: fftw: Build SIMD codelets.
Date: Tue, 08 May 2018 19:29:04 -0400 [thread overview]
Message-ID: <87h8nhk9q7.fsf@netris.org> (raw)
In-Reply-To: <BN7PR11MB28349A3E6DE1C6486B0FDB3FB79A0@BN7PR11MB2834.namprd11.prod.outlook.com> (Eric Bavier's message of "Tue, 8 May 2018 21:01:29 +0000")
Hi Eric,
Eric Bavier <bavier@cray.com> writes:
> Ok, if you feel confident, that's fine with me.
>
> Otherwise, I have a patch that I've tested on x86-64, and in the
> middle of testing for armhf that I can push in a few hours. I could
> easily add a commit that remove the "--enable-armv7a-cntvct" flag.
Sorry for the duplicate work, but I already pushed my fixes in commit
69d5909e032e2fba57814ea9db52389d384d9341 to core-updates. I tested them
on x86_64, but nowhere else. It's not ideal, and I certainly wouldn't
do such a thing on 'master', but given the large number of affected
builds and my uncertainty about when you would fix it, I didn't want to
wait any longer.
FYI, I also removed "--enable-armv8-cntvct-el0" on 64-bit ARM, because
<https://github.com/FFTW/fftw3/blob/master/README-perfcnt.md> suggests
that as on 32-bit ARM, the relevant instruction is not normally
available from user mode.
I removed "--enable-mips-zbus-timer" on MIPS as well, because I suspect
that it's not supported on Loongson devices, although I'm not certain.
If you see any problems with my commit, please let me know.
Thanks!
Mark
next prev parent reply other threads:[~2018-05-08 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180417212549.1283.62731@vcs0.savannah.gnu.org>
[not found] ` <20180417212551.BB270208E4@vcs0.savannah.gnu.org>
2018-05-03 23:25 ` 01/01: gnu: fftw: Build SIMD codelets Mark H Weaver
2018-05-04 14:44 ` Eric Bavier
2018-05-08 20:56 ` Mark H Weaver
2018-05-08 21:01 ` Eric Bavier
2018-05-08 23:29 ` Mark H Weaver [this message]
2018-05-09 2:29 ` Eric Bavier
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=87h8nhk9q7.fsf@netris.org \
--to=mhw@netris.org \
--cc=bavier@cray.com \
--cc=guix-devel@gnu.org \
/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.