search for: nolegacy

Hi everybody. I'm struggling with setting up an SPTPS connection between two of my machines. I attached the patch that I used to analyze this. Apparently different keys are derived depending on the crypto backend. Is this intentional? Linking to openssl results in char key[] = { 0xb2, 0x9d, 0x8d, 0x24, 0x91, 0x04, 0xaf, 0x25, 0x3f, 0x10, 0x34, 0x9d, 0xc7, 0x73, 0x8c, 0xe1, 0x24, 0x32,

...missing when calling from a LLVM-compiled AVX function to a foreign-compiled SSE function, hence a transition penalty. One possible solution around this issue is to add a function attribute which specifies whether the caller and callee have the same architecture. e.g., extern int foo __attribute__((nolegacy)); would declare an external function that does not use legacy SSE instruction. Any thoughts? - Gao. _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

...missing when calling from a LLVM-compiled AVX function to a foreign-compiled SSE function, hence a transition penalty. One possible solution around this issue is to add a function attribute which specifies whether the caller and callee have the same architecture. e.g., extern int foo __attribute__((nolegacy)); would declare an external function that does not use legacy SSE instruction. Any thoughts? - Gao.

...h setting up an SPTPS connection between two of my > machines. I attached the patch that I used to analyze this. Apparently > different keys are derived depending on the crypto backend. Is this > intentional? No, this is not intentional, it's a bug in the hmac_sha512 implementation in nolegacy/prf.c. I'll fix this. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: &l...