------- Comment From [email protected] 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
> doing wrong?
After digging a bit more, I don't think that will be necessary. I experimented
with this package:
http://ppa.launchpad.net/xnox/nonvirt/ubuntu/pool/main/a/atlas/atlas_3.10.3-8ubuntu1+ppa3.dsc
First I had a bit of trouble with the build, because the "rules" file
doesn't specify the -mzvector flag in the compile options. (Is this the
latest source you've been using?) I patched the rules file accordingly,
adding variables with additional config options for z13 and z14, where
the z13 version looks like this:
CONF_Z13 := -A IBMz13 -V 8 \
-F acg "$(CPPFLAGS) $(CFLAGS) -march=z13 -mzvector" \
-F xc "$(CPPFLAGS) $(CFLAGS)" \
-F if "$(FFLAGS) -march=z13"
And using the variables like this:
ifeq ($(Z13),yes)
mkdir -p build-z13
cd build-z13 && ../configure $(CONFIGURE_FLAGS) $(CONF_Z13)
endif
Note that I ask Atlas to exclude the "march" and "mzvector" options for
the "xc" group of compilations. This might be a first step towards
"cross-compilation".
After that, the build worked on z14 and created vector-enabled binaries
for z13 and z14 which seem to yield reasonable performance. But then the
"*.install" files gave me trouble, and instead of completing the build
of the .deb files, I got error messages like this:
make[1]: Entering directory '/home/arnez/atlas-3.10.3'
dh_install
dh_install: Cannot find (any matches for) "yes" (tried in ., debian/tmp)
dh_install: Cannot find (any matches for) "yes" (tried in ., debian/tmp)
...
This obviously originates from the "${Z13}" and "${Z14}" in the
"*.install" files, e.g.:
[s390x] ${Z13} build/libatlas.so.*
/usr/lib/${DEB_HOST_MULTIARCH}/z13
After removing all occurrences of "${Z13}" and "${Z14}", the build
completed with a warning "dh_missing: usr/lib/s390x-linux-
gnu/libsatlas.so exists in debian/tmp but is not installed to anywhere."
However, the resulting ".deb" files contained the wrong shared libraries
for z13 and z14! Instead of using the libraries built under "build-z13"
and "build-z14", the library under "build" was replicated three times.
This is obviously due to an error in the "*.install" files as well,
where the build-z13 and build-z14 aren't referenced at all.
I hope this helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814796
Title:
[19.04 FEAT] Provide optimized libatlas libraries for different types
of z Systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814796/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
