--- Log opened Fri Mar 29 00:00:29 2019 08:25 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 255 seconds] 08:26 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1 14:17 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 244 seconds] 17:24 -!- echonaut [~echonaut@46.101.192.134] has joined #secp256k1 20:07 < sipa> this is annoying... apparently if you shift a 32-bit int by a 64-bit value, the result is 32 bits by the C spec 20:07 < sipa> MSVC however guesses you're making a mistake, makes it return a 64-bit value violating the spec, but gives a warning if you set the warning level high enough 20:08 < gmaxwell> sipa: what happens if you cast specifically? 20:08 < sipa> then it works fine 20:09 < sipa> ah, i'm wrong; the compiler is guessing based on the context that you want a 64-bit result, and then actually computes a 64-bit result 20:10 < sipa> we know in this case that the result is never more than 1<<13, so the warning is kinda stupid 20:12 < sipa> the code is more obviously correct by starting with a 64-bit value, though 20:12 < sipa> so i'll just PR that 20:13 < sipa> oh i misread; it's not actually violating the spec; it's just warning for the implicit conversion from 32 to 64 bit 21:36 < midnightmagic> lol --- Log closed Sat Mar 30 00:00:31 2019