From: Mo Zhou <lumin@debian.org>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] [GSoC] Weekly Report: July 1 - July 7 | BLAS/LAPACK Runtime Switch
Date: Sat, 06 Jul 2019 19:23:41 -0700 [thread overview]
Message-ID: <fbce8969ade2d3ffdcc5b9738551cce3@debian.org> (raw)
Hi list,
This week I
1. finalized the sci-libs/openblas ebuild file
and got it merged into ::gentoo.
2. bumped version for sci-libs/blis
3. tried to build all reverse dependencies of
sci-libs/{blas,cblas,lapack}-reference and
virtual/{blas,cblas,lapack} to scan for
possible regression. Result is available
here [1].
For some important software I also ran
unittests, for example numpy and octave.
4. fixed dependency information for two packages
during the build test.
5. Wrote a preliminary documentation about the
usage and the project [2]
Next I'm going to integrate intel's math kernel
library into this mechanism. By the mid-July
we would be able to present the document to
more audience and have the mechanism more widely
tested.
Maybe I'm a little bit ahead of schedule at this
point as all targets have almost been completed.
The fact that I'm maintaining a similar mechanism
for Debian isn't the main reason for this -- It's
the (unexpected) mechanism redesign that had
reduced the amount of work. This should be fine
as the new design is much better and smoother
compared to the original one.
I talked with Benda about the problem. We think
Gentoo prefox / portage + Debian integration
may be the next problem to look into.
[1] https://github.com/cdluminate/my-overlay/blob/master/checklist.txt
[2] https://github.com/cdluminate/my-overlay/blob/master/usage.md
next reply other threads:[~2019-07-07 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 2:23 Mo Zhou [this message]
2019-07-07 9:54 ` [gentoo-soc] Weekly Report: July 1 - July 7 | BLAS/LAPACK Runtime Switch Benda Xu
2019-07-07 12:11 ` [gentoo-soc] [GSoC] " Benda Xu
2019-07-07 12:18 ` Mo Zhou
2019-07-07 18:10 ` Andrew Savchenko
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=fbce8969ade2d3ffdcc5b9738551cce3@debian.org \
--to=lumin@debian.org \
--cc=gentoo-soc@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox