Now that testing is up, we can return to the code. I'd prefer to do things incrementally. I've created a branch "s390x", with basic configure setup and the README file from your merge request.
Next, I think it makes sense to start with adding the basic aes functions. From a quick look at the MR, it seems the aes instructions don't want any explicit key schedule with expanded subkeys, but wants the raw key? Same for encrypt and decrypt? It would make sense to me with one file each under s390x/msa_x1 for the functions being replaced, but then the current aes-encrypt.c would also need to be split accordingly. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list [email protected] http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
