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