--- Comment From ar...@de.ibm.com 2019-06-26 11:19 EDT---
> This bug was fixed in the package atlas - 3.10.3-8ubuntu3
Sorry, this hasn't worked.
While the above package is indeed contained in the pool (at
http://ports.ubuntu.com/ubuntu-ports/pool/universe/a/atlas/), it doesn't
appear in an
--- Comment From heinz-werner_se...@de.ibm.com 2019-05-06 05:41 EDT---
IBM bugzilla status -> closed, Fix Released for disco in support of z13.
For z14 support a new ticket will be opened against Ubuntu 19.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
--- Comment From ar...@de.ibm.com 2019-04-01 11:35 EDT---
> 3.10.3-8ubuntu2 is now published in the same repository, and should be
> better.
Right. I tested libatlas3-base and can confirm that it contains the
vector-enabled library in the z13 directory. Now the library performs as
expec
--- Comment From ar...@de.ibm.com 2019-03-25 10:40 EDT---
> 1) Please re-review sources from the correct location
> (ci-train-ppa-service urls above)
OK, these look better, but the main issue remains the same:
$ cd atlas-3.10.3/debian
$ grep build-z13 *.install
$ grep build-z14 *.install
On Fri, 22 Mar 2019 at 19:15, bugproxy wrote:
>
> --- Comment From ar...@de.ibm.com 2019-03-22 15:02 EDT---
> > Can you perchance provide a full build-log, of how you build the library
> > locally for z13 (without any debian/ubuntu packaging) and get the exepcted
> > performance? Such that
--- Comment From ar...@de.ibm.com 2019-03-22 15:02 EDT---
> Can you perchance provide a full build-log, of how you build the library
> locally for z13 (without any debian/ubuntu packaging) and get the exepcted
> performance? Such that i can dig into that build log to figure out what i am
>
--- Comment From s...@de.ibm.com 2019-03-21 04:47 EDT---
I've just committed the glibc patch "S390: Mark vx and vxe as important hwcap."
(https://sourceware.org/git/?p=glibc.git;a=commit;h=61f5e9470fb397a4c334938ac5a667427d9047df)
to glibc-master-branch
and cherry-picked it on the glibc 2
--- Comment From s...@de.ibm.com 2019-03-20 05:37 EDT---
As already mentioned in Andreas' comment, vx and vxe is currently not part of
the "important" hwcaps.
I've just posted the patch "S390: Mark vx and vxe as important hwcap."
(https://www.sourceware.org/ml/libc-alpha/2019-03/msg00401.
--- Comment From andreas.kreb...@de.ibm.com 2019-03-19 04:30 EDT---
I think the subdirs for z13 should be vx and for z14 vx/vxe. These are the
hardware facilities as stated in /proc/cpuinfo plus the commitment from the
Linux kernel to save and restore vector registers. For z14 both facili
--- Comment From ar...@de.ibm.com 2019-03-18 14:14 EDT---
> Added -mzvector, fixed up a few more packaging bits, and it looks like z13
> optimized libraries are fully built.
Hm, I've tried /usr/lib/s390x-linux-gnu/z13/libatlas.so.3.10.3. The sgemm/dgemm
kernels from this library don't use
--- Comment From andreas.kreb...@de.ibm.com 2019-03-15 04:29 EDT---
(In reply to comment #18)
...
> z13 adds -A IBMz13 -V 8 config options, and -march=z13 to all the *flags
> z14 adds -A IBMz14 -V 4 config options, and -march=z14 to all the *flags
> and no -mzvector is not used at the momen
--- Comment From andreas.kreb...@de.ibm.com 2019-03-14 12:34 EDT---
The should be an -mzvector option somewhere to enable the high level vector
data types. Wasn't that part of the libatlas flags for IBM Z?
Would it suffice if we would run the libatlas z14 testsuite and provide
you with th
12 matches
Mail list logo
