Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
clang/test/CodeGen/X86/rdrand-builtins.c | ||
---|---|---|
19–20 | why do you still need the #if-else-endif? |
clang/lib/Headers/immintrin.h | ||
---|---|---|
296 | variable names in intrinsic headers must start with 2 underscores. |
clang/lib/Headers/immintrin.h | ||
---|---|---|
296 | What about this comment? |
clang/lib/Headers/immintrin.h | ||
---|---|---|
297 | Are there any sideeffects that we might encounter by not always performing both __builtin_ia32_rdrand32_step calls? unsigned int __lo, __hi; int __res_lo = __builtin_ia32_rdrand32_step(&__lo); int __res_hi = __builtin_ia32_rdrand32_step(&__hi); if (__res_lo && __res_hi) { *__p = ((unsigned long long)__hi << 32) | (unsigned long long)__lo; return 1; } else { *__p = 0; return 0; } |
clang/lib/Headers/immintrin.h | ||
---|---|---|
297 | however, if the first rdrand32 failed, then we don't need to execute the second one. |
clang/lib/Headers/immintrin.h | ||
---|---|---|
297 | I understand that - but given randomizers are often used for sensitive applications (crypto) - my question was whether not always calling this twice was going to affect things. |
variable names in intrinsic headers must start with 2 underscores.