From: Chris Marusich <cmmarusich@gmail.com>
To: Eric Bavier <bavier@cray.com>
Cc: guix-devel@gnu.org
Subject: Re: fftw runtime cpu detection
Date: Fri, 06 Apr 2018 00:54:19 -0700 [thread overview]
Message-ID: <87po3cahxw.fsf@gmail.com> (raw)
In-Reply-To: <20180405221329.GT105827@pe06.us.cray.com> (Eric Bavier's message of "Thu, 5 Apr 2018 17:13:29 -0500")
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Eric Bavier <bavier@cray.com> writes:
> I recently discovered that the FFTW library can do runtime cpu
> detection.
Cool! I'm not familiar with this library, but the patch seems pretty
reasonable to me.
> In order to do this, the package needs to be configured to build SIMD
> "codelets", like how our 'fftw-avx' currently does. Then, based on
> the instruction support detected at runtime, make those kernels
> available to the fftw "planner" for execution.
So, if we choose the right configure flags at build time (for the given
architecture), then at runtime, the software will detect the CPU and
either perform better or make more features available. Is that right?
I see you added the "--enable-sse" configure flag, and it not present
before. Why did you add it?
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-04-06 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 22:13 fftw runtime cpu detection Eric Bavier
2018-04-06 7:54 ` Chris Marusich [this message]
2018-04-06 15:08 ` Eric Bavier
2018-04-06 8:05 ` Ludovic Courtès
2018-04-06 15:02 ` Eric Bavier
2018-04-06 15:09 ` Ludovic Courtès
2018-04-06 18:37 ` Marius Bakke
2018-04-17 21:29 ` Eric Bavier
2018-04-18 21:36 ` Ludovic Courtès
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=87po3cahxw.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--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 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).