2025/01/23

Newest at the top

2025-01-23 20:03:24 +0100euphores(~SASL_euph@user/euphores) (Quit: Leaving.)
2025-01-23 20:00:11 +0100simplystuart(~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 252 seconds)
2025-01-23 19:57:59 +0100alecs(~alecs@61.pool85-58-154.dynamic.orange.es) (Ping timeout: 252 seconds)
2025-01-23 19:55:46 +0100simplystuart(~simplystu@c-75-75-152-164.hsd1.pa.comcast.net)
2025-01-23 19:54:39 +0100 <haskellbridge> <sm> I'd say that is a long shot. Darcs is a big crufty old codebase.
2025-01-23 19:54:17 +0100Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) Tuplanolla
2025-01-23 19:53:40 +0100alecs(~alecs@61.pool85-58-154.dynamic.orange.es) alecs
2025-01-23 19:50:51 +0100 <homo> also having darcs on riscv would be very neat, which again is more realistic to do with microhs
2025-01-23 19:46:52 +0100Lord_of_Life_Lord_of_Life
2025-01-23 19:44:47 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 252 seconds)
2025-01-23 19:44:39 +0100nhar(~noah@host-68-169-128-200.BROOLT1.epbfi.com) (Ping timeout: 260 seconds)
2025-01-23 19:43:58 +0100Lord_of_Life_(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2025-01-23 19:43:07 +0100tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh
2025-01-23 19:41:51 +0100simplystuart(~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 252 seconds)
2025-01-23 19:41:35 +0100xdminsy(~xdminsy@117.147.71.143) xdminsy
2025-01-23 19:41:24 +0100wootehfoot(~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer)
2025-01-23 19:40:52 +0100sord937(~sord937@gateway/tor-sasl/sord937) (Quit: sord937)
2025-01-23 19:40:46 +0100xdminsy(~xdminsy@117.147.71.143) (Ping timeout: 252 seconds)
2025-01-23 19:38:39 +0100 <homo> as well as on any other instruction set architecture that is either 32-bit or 64-bit
2025-01-23 19:38:02 +0100 <homo> well, it's small size (or rather design decision) already allows it to be more portable than ghc, it should build on riscv without any modifications
2025-01-23 19:34:51 +0100 <haskellbridge> <sm> sounds great! This should be helpful for microhs' portability in the end
2025-01-23 19:32:14 +0100__monty__(~toonn@user/toonn) toonn
2025-01-23 19:31:52 +0100__monty__(~toonn@user/toonn) (Quit: leaving)
2025-01-23 19:30:41 +0100vgtw(~vgtw@user/vgtw) vgtw
2025-01-23 19:28:58 +0100 <homo> s/work yacc/work with yacc/
2025-01-23 19:28:39 +0100 <homo> a cherry on top I need to figure out how to work yacc and extend hugs to support pattern guards so that there is no need for long bootstrap chain in the future
2025-01-23 19:27:24 +0100 <homo> sm well, bootstrap with hugs is complete, so now it's possible for me to focus on porting, all I need to do is simply rewrite everything that expects posix environment into using plan9 environment, both virtual machine and provided haskell source have posix-specific code (which means generated/mhs.c is not portable despite being for virtual machine)
2025-01-23 19:26:07 +0100sprotte24(~sprotte24@p200300d16f0615004cac1667a189cb83.dip0.t-ipconnect.de)
2025-01-23 19:23:58 +0100xdminsy(~xdminsy@117.147.71.143) xdminsy
2025-01-23 19:23:33 +0100xdminsy(~xdminsy@117.147.71.185) (Ping timeout: 246 seconds)
2025-01-23 19:23:02 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 244 seconds)
2025-01-23 19:22:31 +0100vgtw(~vgtw@user/vgtw) (Quit: ZNC - https://znc.in)
2025-01-23 19:21:41 +0100j1n37(~j1n37@user/j1n37) (Ping timeout: 252 seconds)
2025-01-23 19:20:13 +0100ubert(~Thunderbi@2a02:8109:ab8a:5a00:9d6f:fc2a:19b6:b502) (Remote host closed the connection)
2025-01-23 19:19:50 +0100simplystuart(~simplystu@c-75-75-152-164.hsd1.pa.comcast.net)
2025-01-23 19:18:35 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-01-23 19:18:01 +0100ColinRobinson(~juan@user/JuanDaugherty) (Quit: praxis.meansofproduction.biz (juan@acm.org))
2025-01-23 19:16:50 +0100 <haskellbridge> <sm> homo: sounds like you want to bring microhs to plan 9 ? what's the current problem ?
2025-01-23 19:15:10 +0100j1n37(~j1n37@user/j1n37) j1n37
2025-01-23 19:12:06 +0100jespada(~jespada@2800:a4:2317:8200:52e:e131:1453:b068) (Quit: My Mac has gone to sleep. ZZZzzz…)
2025-01-23 19:10:49 +0100j1n37-(~j1n37@user/j1n37) (Ping timeout: 260 seconds)
2025-01-23 19:07:36 +0100euleritian(~euleritia@dynamic-176-006-148-054.176.6.pool.telefonica.de)
2025-01-23 19:06:30 +0100euleritian(~euleritia@77.23.250.232) (Ping timeout: 276 seconds)
2025-01-23 19:03:21 +0100cy7(~yt@pool-99-238-69-14.cpe.net.cable.rogers.com)
2025-01-23 19:00:05 +0100JuanDaughertyColinRobinson
2025-01-23 18:57:10 +0100 <homo> also if someone seriously considers trying to build ghc with microhs, most likely it will take 1000 times longer to compile, so even if 5 hours turn into 1000 hours, that is almost 42 days waiting for compilation to finish, and you will have to start again if something fails and you make changes to ghc
2025-01-23 18:56:15 +0100vpan(~vpan@212.117.1.172) (Quit: Leaving.)
2025-01-23 18:55:08 +0100nhar(~noah@host-68-169-128-200.BROOLT1.epbfi.com)
2025-01-23 18:54:25 +0100j1n37(~j1n37@user/j1n37) (Ping timeout: 248 seconds)
2025-01-23 18:53:55 +0100j1n37-(~j1n37@user/j1n37) j1n37