--- Day changed Fri Jun 22 2018
00:15 -!- kallewoof [~karl@240d:1a:759:6000:a7b1:451a:8874:e1ac] has quit [Ping timeout: 245 seconds]     
06:12 -!- jtimon [~quassel@40.28.134.37.dynamic.jazztel.es] has quit [Ping timeout: 256 seconds]     
06:53 -!- jtimon [~quassel@40.28.134.37.dynamic.jazztel.es] has joined #secp256k1     
07:29 -!- roconnor [~roconnor@host-45-58-224-191.dyn.295.ca] has joined #secp256k1     
07:38 < roconnor> gmaxwell: the VERIFY_CHECK(a != b) goes into secp256k1_fe_mul at the same place where the VERIFY_CHECK(r != b) already exists.  So I guess they both will get compiled away.  sipa: do you know if SECP256K1_RESTRICT is disabled when VERIFY is enabled during tests?
07:49 < gmaxwell> roconnor:  it is.
07:49 < gmaxwell> (for that reason, now that you mention it)
09:55 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]     
09:58 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1     
14:06 -!- roconnor [~roconnor@host-45-58-224-191.dyn.295.ca] has quit [Ping timeout: 245 seconds]