On Fri, 22 Mar 2019 at 19:15, bugproxy <[email protected]> wrote: > > ------- 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 >
... which is an obsolete source that never even managed to compile, and not install any libraries ever. And it has been deleted and longer published, but not yet garbage collected by launchpad. And below, you seem to be repeating the steps that were already done. Please don't use that source package.... The source and binaries, that we are currently evaluating are from this ppa: """ Please test: sudo add-apt-repository ppa:ci-train-ppa-service/3679 sudo apt-get update """ You can enable source repository for that ppa too, to "apt-get source atlas". Or if you need more URLs to build logs please see: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3679 https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3679/+build/16500359 http://ppa.launchpad.net/ci-train-ppa-service/3679/ubuntu/ http://ppa.launchpad.net/ci-train-ppa-service/3679/ubuntu/pool/main/a/atlas/ However, you prefer to fetch / analyse that. (launchpad PPA, build record, apt-get archive, the pool location of atlas) > 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, It is not =) note the compilation and installations were fixed up for the better in the above ci-train-ppa-service ppa.... > 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". > I'll try above. However, note that the above PPA, there is -march=z13 -mzvector flags passed, yet I was told earlier that it did not produce vector enabled binaries. I'll see if "xc" group of flags helps with building z14 atlas on z13, this is helpful. My questions are still not answered as both '-march=z13 and -mzvector' flags are in used in that ppa, and it is claimed that no vector optimized libraries are produced. Where the wrong binaries tested, i.e. those from the generic Ubuntu archive, rather than from the ci-train-ppa? 1) Please re-review sources from the correct location (ci-train-ppa-service urls above) 2) Please re-review binaries from the correct location to see if they are vector enabled or not. 3) Whilst doing above, please paste the output of $ apt-cache policy libatlas3-base ps. i am sorry for causing any confusion due to change of the location of where the builds are located. pss. I am away from the office until April -- Regards, Dimitri. ** Changed in: ubuntu-z-systems Status: Triaged => Incomplete -- 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
