Oliver Roberts

Ok, so it isn't crashing, but just not working correctly? There are a few things that somehow got messed up in the AmiSSL 4.3 release. First thing I would suggest...

AFAIK, Tabor doesn't have AltiVec, right? In which case attached is the non-AltiVec sha256 code: [sha256-ppc.s.txt](https://github.com/jens-maus/amissl/files/4014163/sha256-ppc.s.txt) Could still be that the problem is elsewhere though.

Hmmm... I'm not sure there is a way around it other than blacklisting. It seems r2 was chosen and ExecSG's previous use of r2 for baserel abandoned. Bad choice IMHO....

There were already some discussions about using small data, but isn't that restricted to 64K? OpenSSL's data usage (excluding rodata) is already over 32K and unfortunately it will most likely...

@jens-maus I've sent you an email to follow up on the last one I sent n September - not sure if you received it? I'm not sure YAM is a...

Have been taking another look at switching from r2 to r13, but it is looking like a non-starter to me. In OpenSSL 3.0.4, we currently have data of 47K (excluding...

Ok. The problem is still going to be when OpenSSL inevitably goes beyond 64K, unfortunately. Currently the OS3 build of OpenSSL is using 32-bit offsets for a4 relative data, similar...

First, ensure you don't have any conflicting includes installed - if regular OpenSSL includes are in the include search path, as well as the AmiSSL variants, this will cause problems....

Hmmm... I've been looking into this, but don't really know what to suggest as I don't have StormC. All I know is that I have the AmiSSL includes working fine...

@ThoughtCheese72 Well, if there is anything I can do to make the AmiSSL includes more compatible with StormC, I'm happy to do so. It's just the the error messages given...