On Wednesday, September 23, 2015 at 3:37:25 AM UTC-4, [email protected] wrote: > > > > Am Mittwoch, 23. September 2015 00:54:54 UTC+2 schrieb Jeffrey Walton: >> >> >> Can you download the latest RC4, fix it under Windows, and then send >> config.h back to me? >> > > Sure, I have attached a patch for the config.h from the current RC4. >
Thanks Marcel, got it. I'll get you something new in a few hours. I think we've got a grasp on the changes needed for X32 ASM. We're at the point the overall strategy is/can be: enable X32 ASM (like X86 and X64), but disable it on a translation unit if the port to X32 was unsuccessful. Related, see https://github.com/weidai11/cryptopp/issues/32. We need to rework this from rijndael.h to accommodate X32 ASM: class CRYPTOPP_DLL CRYPTOPP_NO_VTABLE Enc : public Base { public: void ProcessAndXorBlock(const byte *inBlock, const byte *xorBlock, byte *outBlock) const; #if (CRYPTOPP_BOOL_X64 || CRYPTOPP_BOOL_X86) size_t AdvancedProcessBlocks(const byte *inBlocks, const byte *xorBlocks, byte *outBlocks, size_t length, word32 flags) const; #endif }; The "#if (CRYPTOPP_BOOL_X64 || CRYPTOPP_BOOL_X86)" does not quite capture things now. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
