2026/06/19

Newest at the top

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
2026-06-19 13:20:27 +0000xstill_(xstill@fimu/xstill) xstill
2026-06-19 13:16:20 +0000tabaqui(~tabaqui@167.71.80.236) tabaqui
2026-06-19 13:14:50 +0000spew(~spew@user/spew) spew
2026-06-19 13:08:29 +0000ryou(~haze@user/ryou) ryou
2026-06-19 13:06:45 +0000lossless(~haze@user/ryou) (Read error: Connection reset by peer)
2026-06-19 13:00:09 +0000xstill_(xstill@fimu/xstill) (Quit: Ping timeout (120 seconds))
2026-06-19 12:45:53 +0000tromp(~textual@2001:1c00:340e:2700:ed09:73b3:83dd:1e97) (Quit: My iMac has gone to sleep. ZZZzzz…)
2026-06-19 12:27:46 +0000tabaqui(~tabaqui@167.71.80.236) (Ping timeout: 276 seconds)
2026-06-19 12:27:39 +0000kuribas(~user@2a02-1810-2825-6000-bca6-dcdf-e0b2-2d0e.ip6.access.telenet.be) kuribas
2026-06-19 12:23:54 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-19 12:21:43 +0000szkl(uid110435@id-110435.uxbridge.irccloud.com) (Quit: Connection closed for inactivity)
2026-06-19 12:21:37 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2026-06-19 12:16:25 +0000xff0x(~xff0x@2405:6580:b080:900:7423:ed7:4abd:dce)
2026-06-19 12:15:25 +0000Googulator(~Googulato@team.broadbit.hu)
2026-06-19 11:47:56 +0000emilym(~Thunderbi@user/emilym) emilym
2026-06-19 11:47:15 +0000emilym(~Thunderbi@user/emilym) (Ping timeout: 245 seconds)
2026-06-19 11:40:34 +0000CiaoSen(~Jura@2a02:3100:6164:f000:4e50:ddff:fe9b:8922) (Ping timeout: 248 seconds)
2026-06-19 11:34:34 +0000 <[exa]> I'll go with the pop one and switch in case it starts failing
2026-06-19 11:33:55 +0000 <[exa]> <<<- usability maintainability ->>>