--- Log opened Wed May 24 00:00:10 2023
02:16 -!- jon_atack [~jonatack@user/jonatack] has quit [Quit: WeeChat 3.8]
02:52 -!- jonatack [~jonatack@user/jonatack] has joined #secp256k1
03:08 < hebasto> real_or_random: prebuilt task has been just finished -- https://cirrus-ci.com/task/6710970463027200; will it help to restart dependent MSVC tasks?
06:12 < real_or_random> hebasto: ah sorry I didn't see your message here
06:13 < hebasto> nm :) I also was digging into that problem...
06:13 < real_or_random> want to ACK https://github.com/bitcoin-core/secp256k1/pull/1327 (assuming CI finishes)?
06:13 < real_or_random> the last job did just start
06:13 < hebasto> testing it in personal cirrus account right now
06:14 < real_or_random> I could reproduce the issue by building the docker image locally, that was easier for debugging 
06:14 < hebasto> oh, good to know it
06:15 < real_or_random> you can run  docker build . -f ci/linux-debian.Dockerfile (add --no-cache --pull to force rebuild) 
06:16 < real_or_random> this gives you a hash $HASH and then you can run: docker run -it  --mount type=bind,src=/path/to/your/secp256k1,dst=/root/secp256k1 $HASH (where the mount is optional of course, but usually useful)
06:17 < hebasto> ty
06:36 < roconnor> real_or_random: what does polyfilling mean?
06:37 < real_or_random> roconnor: "providing a drop-in implementation of a feature that some thing doesn't have" but usually it's "without the calling code even noticing"
06:38 < real_or_random> I guess the usage of this term is stretched a bit here...
06:40 < real_or_random> I think this is common in javascript where you can have introspection and can define and re-define even built-in. there it's often used if a browser lacks a feature. say firefox doesn't support browser-provided javascript function XYZ(). then you include a "polyfill" that redirects XYZ to a user-provided implementation of XYZ  in firefox
06:40 < real_or_random> s/built-in/built-in features
06:41 < real_or_random> lmgtfy https://en.wikipedia.org/wiki/Polyfill_(programming)
07:24 < hebasto> it seems "arm64 ..." CI tasks are not parallelized very well
08:04 -!- preimage [~halosghos@user/halosghost] has joined #secp256k1
09:13 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
09:14 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 240 seconds]
10:39 -!- siv2r [~siv2rmatr@2001:470:69fc:105::fed3] has joined #secp256k1
10:59 < roconnor> sipa: https://arxiv.org/pdf/2211.10665.pdf on 14 has a Coq data structure for a subset of x86-64 assembly, suggesting they have their own mini model of x86.
12:32 -!- roconnor [~quassel@coq/roconnor] has quit [Ping timeout: 246 seconds]
12:33 -!- roconnor [~quassel@coq/roconnor] has joined #secp256k1
13:27 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Read error: Connection reset by peer]
14:12 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 3.8]
--- Log closed Thu May 25 00:00:11 2023