From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <ericbavier@centurylink.net>
Cc: Eric Bavier <bavier@cray.com>, guix-devel@gnu.org
Subject: Re: fftw runtime cpu detection
Date: Wed, 18 Apr 2018 23:36:33 +0200 [thread overview]
Message-ID: <87po2wryce.fsf@gnu.org> (raw)
In-Reply-To: <20180417162948.44d63d6b@centurylink.net> (Eric Bavier's message of "Tue, 17 Apr 2018 16:29:48 -0500")
Eric Bavier <ericbavier@centurylink.net> skribis:
> Hello Guix,
>
> On Fri, 06 Apr 2018 20:37:42 +0200
> Marius Bakke <mbakke@fastmail.com> wrote:
>
>> Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>>
>> > Eric Bavier <bavier@cray.com> skribis:
>> >
>> >> On Fri, Apr 06, 2018 at 10:05:43AM +0200, Ludovic Courtès wrote:
>> >>
>> >>> If that’s the case, I’d be in favor of pushing this patch to core-updates.
>> >>
>> >> Great. I'll do some more testing. Should I send a finalized patch to
>> >> guix-patches when it's ready?
>> >
>> > If Marius has no objections, I think you could push it directly to
>> > core-updates.
>>
>> Sounds good to me. I just pushed a couple of full-rebuild commits to
>> fix bootstrap-tarballs, so the Big Rebuild is still some days off.
>
> I just pushed commit 65bb22796f854cbc3eae053a80b1d64365dad376 to
> core-updates. I built a good portion of fftwf's dependents to check
> things out. The dependent audio libraries seemed to pass their tests
> on the build machine (an avx cpu), which gives me confidence.
Awesome, thank you!
Ludo’.
prev parent reply other threads:[~2018-04-18 21:36 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
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 [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=87po2wryce.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bavier@cray.com \
--cc=ericbavier@centurylink.net \
--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).