[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Packaging BLIS
From: |
Ludovic Courtès |
Subject: |
Packaging BLIS |
Date: |
Thu, 07 Sep 2017 17:51:15 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Hello,
Dave Love <address@hidden> skribis:
> Ludovic Courtès <address@hidden> writes:
[...]
>> >> One example which has been investigated, and you can't, is BLIS. You
>>
>> (Why “you can’t?” It’s free software AFAICS on
>> <https://github.com/flame/blis/tree/master>.)
>
> Well, you could embark on some sort of (GCC-specific?) re-write, but it
> would be better to work on <https://github.com/flame/blis/issues/129>.
> I don't think there's anywhere you can just attach GCC attributes, and
> certainly no magic will happen for currently-unsupported architectures.
That caught my attention so I packaged BLIS:
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=5a7deb117424ff4d430b771b50e534cf065c0ba1
There are several “flavors” of BLIS, so you can always rebuild your
favorite program with:
--with-input=openblas=blis-haswell
and similar (or even ‘--with-graft=blis=blis-haswell’ where applicable).
Hopefully the issue you linked to above will be fixed in future versions
of BLIS, at which point we can probably provide a single “blis” package.
Ludo’.