--- Log opened Wed May 05 00:00:46 2021
04:03 < real_or_random> gmaxwell: Can I have your opinion on https://github.com/bitcoin-core/secp256k1/pull/700#issuecomment-780895578 ? I'm not sure what other projects do with -g
09:30 < real_or_random> gmaxwell: re #925: yeah not sure why he didn't include the comment now but let's get it merged then ^^
10:10 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 240 seconds]
10:17 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
10:21 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 260 seconds]
10:26 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
10:31 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
10:31 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 268 seconds]
10:36 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 260 seconds]
10:38 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
10:43 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 252 seconds]
10:45 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
10:46 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
10:50 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 265 seconds]
10:51 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 252 seconds]
10:55 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
10:59 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 246 seconds]
11:00 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
11:03 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
11:04 -!- luke-jr- [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
11:04 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 240 seconds]
11:08 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 265 seconds]
11:09 -!- luke-jr- [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 260 seconds]
11:13 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
11:16 -!- luke-jr- [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
11:17 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
11:18 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 260 seconds]
11:19 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
11:20 -!- luke-jr- [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 252 seconds]
11:22 -!- luke-jr- [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
11:22 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 260 seconds]
11:24 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 268 seconds]
11:26 -!- luke-jr- is now known as luke-jr
12:11 < real_or_random> is this just my feeling or do we really hit every single bug on Cirrus CI? ^^
12:11 < sipa> haha
12:12 < real_or_random> I mean, I'm pretty happy tbh, they're very very responsive
12:13 < real_or_random> but it seems every PR hits some new weird corner case. I guess that's one more reason to reduce the number of tasks ^^
12:15 < gmaxwell> Is there a particular reason to not have fewer tasks but have the tasks do more?
12:16 < real_or_random> I guess my eagerness in reporting bugs is also just way above the average ^^
12:17 < real_or_random> gmaxwell: well, except for possible timeouts, no. I think it's currently just a natural way of creating a task matrix
12:18 < sipa> there is some overhead per-task of course (docker cloning etc) but i think that's still fairly small compared to the actual work done in even the shortest jobs
12:18 < real_or_random> we could change it to reduce the number of tasks but maybe this would make our code less natural. (and the results table may not look so nice, idk)
12:18 < real_or_random> right, I mean that's the point of prebuilding a docker image (with all the apt-get etc).
12:19 < sipa> yeah the pre-building is very cool
14:06 < gmaxwell> real_or_random: would you like to open a PR to add that comment to the headers in contrib?  -- the include-guarding the include is kinda weird and probably deserves the comment you wrote.
14:15 < gmaxwell> sipa: Getting really close to "gcc -O2 -g -Wall -Wextra -c ./src/secp256k1.c -DENABLE_MODULE_SCHNORRSIG"  being a perfectly good way to build the library!  Can I try to covince everyone that just *always* using static tables, shipping a couple configs (as seperate header files) switchable via settings like -DSECP256K1_LOWMEM_SIGN=1 (and, of coure, an analogous ./configure flag)?
14:22 < gmaxwell> (and then the generate tool, regardless if it stays in C or turns into python, just becomes a development tool that isn't built by default and is only used when someone wants a non-standard configuration.)
14:39 < sipa> gmaxwell: yeah, i think we should go ahead with that
14:46 < gmaxwell> \O/  hero to the embedded world.
14:47 < gmaxwell> I think it'll be useful to be able to seperately size sign/verify contexts because there are some applications that need both operations but don't care about the performance of one of them.  E.g. most hardware wallets will still want verify, but it doesn't matter if it's kinda slow.
17:02 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection reset by peer]
17:03 -!- belcher [~belcher@unaffiliated/belcher] has joined #secp256k1
18:52 -!- Netsplit *.net <-> *.split quits: Madars, niftynei, sanketcell
18:54 -!- Netsplit over, joins: sanketcell, Madars, niftynei
19:21 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Ping timeout: 240 seconds]
22:30 -!- dr_orlovsky [~dr-orlovs@31.14.40.19] has quit [Quit: ZNC 1.8.0 - https://znc.in]
22:48 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #secp256k1
--- Log closed Thu May 06 00:00:47 2021