1 2016-07-21 03:49:03 <StephenM347> if anyone has a sec, why does segwit use OP_0 through OP_16 as the version identifiers instead of pushing a 4 byte integer on the stack, for example? seems prohibitive to only allow 16 script upgrades
2 2016-07-21 05:23:18 <roasbeef> StephenM347: there're actually 16*2^8 versions in the latest iteration of segwit. a witness program is OP_0-OP_16 followed by a 2-40 byte datapush. assuming a 32-byte hash then one can interpret the leading 8 bytes as a modifier to the original small integer
3 2016-07-21 05:58:41 <luke-jr> roasbeef: OP_0 can only have the original 20 or 32 byte payload though
4 2016-07-21 05:58:56 <luke-jr> so (15*(2^8)) + 2 :p
5 2016-07-21 08:17:06 <jl2012> luke-jr: no, OP_1 to OP_16 are free, i.e.  (16*(2^8)) + 2
6 2016-07-21 12:00:53 <rafalcpp> hi devrandom, I was wondering - did you ever solved that GCC issue from https://github.com/devrandom/gitian-builder/blob/master/doc/GCC_ISSUES ?
7 2016-07-21 15:59:58 <wumpus> rafalcpp: I don't think those are still issues with newer gcc versions; we don't override any special optimization flags for bitcoin
8 2016-07-21 16:01:50 <wumpus> (and we build with -O2)