When I needed a non-MS/non-Intel (and reasonably un-encumbered) tool to work with the assembly-coded portions of a Common LISP implementation, I found NASM to be quite satisfactory. :)
Also, for others seeing this thread, don't get suckered into various nasm.* domains - the "real" one is nasm.us. Robert On Thu, Jul 23, 2015 at 5:58 PM, Jeffrey Walton <[email protected]> wrote: > The issues with Clang's integrated assembler has got me thinking.... > > Has anyone used NASM with Crypto++? Folks will eventually need an > alternative to utilize gear like AES-NI. > > If we don't provide the ASM for a direct interface, then we will need to > stand-up an ENGINE interface and interface directly with CoreCrypto. > CoreCrypto may be our only choice on iOS (I have never seen a specification > for iOS's hardware/instruction set in this area). > > I was talking to Jack Lloyd, the author of Botan, and he was contemplating > the engine like interface into CoreCrypto. > > Or maybe something else??? > > 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. > -- -- 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.
