2026/06/19

Newest at the top

2026-06-19 17:02:27 +0000hakutaku(~textual@user/hakutaku) hakutaku
2026-06-19 17:00:21 +0000hakutaku(~textual@user/hakutaku) (Quit: My MacBook has gone to sleep. ZZZzzz…)
2026-06-19 16:54:42 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2026-06-19 16:49:24 +0000lisbeths(uid135845@id-135845.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2026-06-19 16:47:49 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-19 16:35:43 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2026-06-19 16:35:23 +0000tabaqui(~tabaqui@167.71.80.236) tabaqui
2026-06-19 16:32:41 +0000vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2026-06-19 16:32:09 +0000peterbecich(~Thunderbi@71.84.33.135) (Ping timeout: 248 seconds)
2026-06-19 16:31:17 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-19 16:27:58 +0000leppard|2(~noOne@ipservice-092-209-218-237.092.209.pools.vodafone-ip.de) (Ping timeout: 244 seconds)
2026-06-19 16:27:24 +0000vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 245 seconds)
2026-06-19 16:24:32 +0000sord937(~sord937@gateway/tor-sasl/sord937) (Quit: sord937)
2026-06-19 16:21:27 +0000peterbecich(~Thunderbi@71.84.33.135) peterbecich
2026-06-19 16:20:30 +0000comerijn(~merijn@77.242.116.146) (Ping timeout: 246 seconds)
2026-06-19 16:17:00 +0000danza(~danza@user/danza) (Remote host closed the connection)
2026-06-19 16:01:48 +0000 <tomsmeding> *our
2026-06-19 16:01:37 +0000 <tomsmeding> comerijn/merijn: clearly the solution is randomising the pass order, then every compile you have a small chance of winning the jackpot ("we compiled out program 1000 times and benchmarked using the best result")
2026-06-19 16:00:52 +0000tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh
2026-06-19 15:59:48 +0000 <tomsmeding> "Unnamed pass: implement Pass::getPassName()" heh
2026-06-19 15:59:05 +0000 <tomsmeding> https://gist.github.com/minjang/89ee4cd6a040dfda0d7dc23603b3c8c3 (don't know if this is accurate, just found via search, but this kind of stuff)
2026-06-19 15:58:27 +0000roconnor(~quassel@rocq/roconnor) ()
2026-06-19 15:57:25 +0000roconnor(~quassel@rocq/roconnor) roconnor
2026-06-19 15:57:20 +0000 <tomsmeding> looping until fixpoint is in those circles considered Not Done as it makes compile time unbounded
2026-06-19 15:56:45 +0000 <tomsmeding> which may include the same pass multiple times, e.g. constant folding in various places in the pipeline
2026-06-19 15:56:19 +0000 <tomsmeding> mauke: traditional compilers have a meticulously hand-tuned optimisation schedule that runs a bunch of passes in a particular order
2026-06-19 15:51:48 +0000ystael(~ystael@user/ystael) ystael
2026-06-19 15:46:08 +0000hiredman(~hiredman@frontier1.downey.family) hiredman
2026-06-19 15:43:01 +0000hiredman(~hiredman@frontier1.downey.family) (Ping timeout: 244 seconds)
2026-06-19 15:34:34 +0000chromoblob(~chromoblo@user/chromob1ot1c) chromoblob\0
2026-06-19 15:34:12 +0000chromoblob(~chromoblo@user/chromob1ot1c) (Read error: Connection reset by peer)
2026-06-19 15:22:43 +0000chromoblob(~chromoblo@user/chromob1ot1c) chromoblob\0
2026-06-19 15:22:15 +0000AlexNoo(~AlexNoo@178.34.163.171) (Ping timeout: 252 seconds)
2026-06-19 15:21:48 +0000chromoblob(~chromoblo@user/chromob1ot1c) (Ping timeout: 256 seconds)
2026-06-19 15:20:23 +0000L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2026-06-19 15:19:09 +0000Sgeo(~Sgeo@user/sgeo) Sgeo
2026-06-19 15:16:51 +0000m(~travltux@user/travltux) travltux
2026-06-19 15:13:45 +0000m(~travltux@user/travltux) (Quit: WeeChat 4.7.2)
2026-06-19 15:11:25 +0000jayanth(~jayanth@69.249.219.205)
2026-06-19 15:10:22 +0000vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2026-06-19 15:07:17 +0000Googulator(~Googulato@team.broadbit.hu) (Ping timeout: 245 seconds)
2026-06-19 14:56:02 +0000 <mauke> ah, fun
2026-06-19 14:55:15 +0000nyc(~nyc@user/nyc) (Remote host closed the connection)
2026-06-19 14:52:43 +0000AlexNoo(~AlexNoo@178.34.163.171)
2026-06-19 14:42:55 +0000wootehfoot(~wootehfoo@user/wootehfoot) (Ping timeout: 264 seconds)
2026-06-19 14:41:33 +0000CiaoSen(~Jura@2a02:3100:6164:f000:4e50:ddff:fe9b:8922) (Ping timeout: 272 seconds)
2026-06-19 14:31:39 +0000tabaqui(~tabaqui@167.71.80.236) (Ping timeout: 252 seconds)
2026-06-19 14:26:21 +0000machinedgod(~machinedg@d108-173-95-19.abhsia.telus.net) machinedgod
2026-06-19 14:11:02 +0000 <comerijn> So before you know it you're trying arbitary permutations and your compiles take as long as an FPGA ;)
2026-06-19 14:10:42 +0000 <comerijn> mauke: It's actually even worse, it's easily conceivable that some sequence of optimisation passes maybe MUCH better than others, and the fixed ordering may prevent you from ever reaching those