2026/06/19

Newest at the top

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
2026-06-19 14:10:30 +0000lisbeths(uid135845@id-135845.lymington.irccloud.com) lisbeths
2026-06-19 14:10:01 +0000leppard(~noOne@ipservice-092-208-182-236.092.208.pools.vodafone-ip.de) (Ping timeout: 244 seconds)
2026-06-19 14:09:55 +0000 <comerijn> it's generally some fixed iterations that are allowed and at some point give up
2026-06-19 14:09:39 +0000AlexNoo(~AlexNoo@178.34.161.132) (Ping timeout: 252 seconds)
2026-06-19 14:09:29 +0000Alex_delenda_est(~al_test@178.34.161.132) (Ping timeout: 245 seconds)
2026-06-19 14:09:22 +0000 <comerijn> Not really
2026-06-19 14:09:04 +0000AlexZenon(~alzenon@178.34.161.132) (Ping timeout: 245 seconds)
2026-06-19 14:07:19 +0000leppard|2(~noOne@ipservice-092-209-218-237.092.209.pools.vodafone-ip.de) Inline
2026-06-19 14:03:00 +0000danza(~danza@user/danza) danza
2026-06-19 14:01:12 +0000 <mauke> is there some clever approach to handle this sort of situation, apart from just running everything repeatedly until things calm down, hopefully?
2026-06-19 14:00:24 +0000 <mauke> for example, constant folding can reveal the static target of a nominally dynamic jump, which can lead to more inlining, which can enable more constant folding
2026-06-19 13:59:22 +0000prdak1prdak
2026-06-19 13:59:12 +0000 <mauke> I've rediscovered something that maybe should have been obvious: optimization passes can expose more work for other optimization passes, so there is no obvious simple way to order them in general
2026-06-19 13:58:37 +0000 <mauke> not haskell specific, but I'm going to ask here anyway
2026-06-19 13:58:17 +0000ft(~ft@p508db6b1.dip0.t-ipconnect.de) ft
2026-06-19 13:58:07 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Read error: Connection reset by peer)
2026-06-19 13:57:36 +0000comerijn(~merijn@77.242.116.146) merijn
2026-06-19 13:57:04 +0000prdak1(~Thunderbi@user/prdak) prdak
2026-06-19 13:56:59 +0000prdak(~Thunderbi@user/prdak) (Read error: Connection reset by peer)
2026-06-19 13:50:00 +0000driib3180(~driib@vmi931078.contaboserver.net) driib
2026-06-19 13:46:59 +0000emilym(~Thunderbi@user/emilym) (Ping timeout: 245 seconds)
2026-06-19 13:42:23 +0000__monty__(~toonn@user/toonn) (Quit: leaving)
2026-06-19 13:39:50 +0000nyc(~nyc@user/nyc) nyc
2026-06-19 13:39:25 +0000nyc(~nyc@user/nyc) (Read error: Connection reset by peer)
2026-06-19 13:26:53 +0000CiaoSen(~Jura@2a02:3100:6164:f000:4e50:ddff:fe9b:8922) CiaoSen