| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| edx7 = info7[3]; | ||
| #else | ||
| #endif | ||
| (void) eax1; (void) ebx1; (void) ecx1; (void) edx1; |
There was a problem hiding this comment.
LOL... definitely fighting against the compiler's idea of best practices here using useless no-op statements as a way to work around it. i wish we could disable a specific warning for a whole block of code. i feel like a future compiler will notice that these are useless and stop considering them a "use".
Sorry, something went wrong.
There was a problem hiding this comment.
It was just the least minimal change to silence the warning :)
Luckily, I think we'll never have to fear that this will ever need a change: that (void) pattern is adapted by all known compilers for ages - and I think this will stay.
Sorry, something went wrong.
There was a problem hiding this comment.
Ideally, we would have used (void) ... in the elif branch but it would be an overkill for foolish consistency.
Sorry, something went wrong.
| (void) eax1; (void) ebx1; (void) ecx1; (void) edx1; | ||
| (void) eax7; (void) ebx7; (void) ecx7; (void) edx7; | ||
| #endif | ||
|
|
There was a problem hiding this comment.
Can you remove the double blank lines L98/L99 please? TiA
Sorry, something went wrong.
|
Oh it was merged :') |
Sorry, something went wrong.
…ython#131299) work around unimportant clang-cl warnings in blake2module.c
| Back | FazBrowse Home | New Git URL |
Fix
we see them two (non-PGO) or three times, because the _freeze_module compiles blake2module.c, too.
I think this is a skip news.