Hi, Niels
Did you get the credentials of the new VM? I'm thinking after adding the address and ssh key of new VM, we can't get the optimized cores of AES tested since enable-msa isn't triggered. We need to push some sort of hard-coded option in configure.ac to get it tested in the VM during ci job.
regards, Mamone
On Mon, May 10, 2021 at 6:13 PM Niels Möller nisse@lysator.liu.se wrote:
David Edelsohn dje.gcc@gmail.com writes:
They are going to create a new VM on a separate Open Source Software Cloud for long-term projects. They will contact you directly with the credentials.
Sounds good. Thanks for the update.
Regards, /Niels
-- Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. Internet email is subject to wholesale government surveillance.
Maamoun TK maamoun.tk@googlemail.com writes:
Did you get the credentials of the new VM?
Yes! I set it up and updated the gitlab config last evening, and I've seen a successfull ci run.
I'm thinking after adding the address and ssh key of new VM, we can't get the optimized cores of AES tested since enable-msa isn't triggered. We need to push some sort of hard-coded option in configure.ac to get it tested in the VM during ci job.
We could either switch it on by default in configure.ac, or add a configure flag in .gitlab-ci.
Once fat build support is added, we will no longer to enable it explicitly, right?
Regards, /Niels
On Wed, May 19, 2021 at 7:20 PM Niels Möller nisse@lysator.liu.se wrote:
Maamoun TK maamoun.tk@googlemail.com writes:
I'm thinking after adding the address and ssh key of new VM, we can't get the optimized cores of AES tested since enable-msa isn't triggered. We need to push some sort of hard-coded option in configure.ac to get it tested in the VM during ci
job.
We could either switch it on by default in configure.ac, or add a configure flag in .gitlab-ci.
Once fat build support is added, we will no longer to enable it explicitly, right?
Right, I prefer to get done with AES accelerators then add fat build support for the added modes at once because of dependency relationships for these modes that add more complexity to s390x-fat.c.
regards, Mamone
nisse@lysator.liu.se (Niels Möller) writes:
We could either switch it on by default in configure.ac, or add a configure flag in .gitlab-ci.
Just pushed a change to .gitlab-ci to pass --enable-s390x-msa, and it seems to work, see
https://gitlab.com/gnutls/nettle/-/jobs/1284895250#L580
Regards, /Niels
nettle-bugs@lists.lysator.liu.se