Newest at the top
2025-01-23 19:18:01 +0100 | ColinRobinson | (~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 +0100 | j1n37 | (~j1n37@user/j1n37) j1n37 |
2025-01-23 19:12:06 +0100 | jespada | (~jespada@2800:a4:2317:8200:52e:e131:1453:b068) (Quit: My Mac has gone to sleep. ZZZzzz…) |
2025-01-23 19:10:49 +0100 | j1n37- | (~j1n37@user/j1n37) (Ping timeout: 260 seconds) |
2025-01-23 19:07:36 +0100 | euleritian | (~euleritia@dynamic-176-006-148-054.176.6.pool.telefonica.de) |
2025-01-23 19:06:30 +0100 | euleritian | (~euleritia@77.23.250.232) (Ping timeout: 276 seconds) |
2025-01-23 19:03:21 +0100 | cy7 | (~yt@pool-99-238-69-14.cpe.net.cable.rogers.com) |
2025-01-23 19:00:05 +0100 | JuanDaugherty | ColinRobinson |
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 +0100 | vpan | (~vpan@212.117.1.172) (Quit: Leaving.) |
2025-01-23 18:55:08 +0100 | nhar | (~noah@host-68-169-128-200.BROOLT1.epbfi.com) |
2025-01-23 18:54:25 +0100 | j1n37 | (~j1n37@user/j1n37) (Ping timeout: 248 seconds) |
2025-01-23 18:53:55 +0100 | j1n37- | (~j1n37@user/j1n37) j1n37 |
2025-01-23 18:51:08 +0100 | wootehfoot | (~wootehfoo@user/wootehfoot) wootehfoot |
2025-01-23 18:50:55 +0100 | Me-me | (~me-me@kc.randomserver.name) |
2025-01-23 18:50:45 +0100 | nhar | (~noah@host-68-169-128-200.BROOLT1.epbfi.com) (Ping timeout: 248 seconds) |
2025-01-23 18:50:44 +0100 | <homo> | keeping my goal to bring haskell to plan9 in mind: 1. ghc on plan9 wouldn't even be able to compile and run 99% of packages on stackage because plan9 is neither posix nor windows compatible, 2. I want to rip off ffi completely and convert every haskell code that I use into calling syscalls provided by kernel, 3. ghc is too bloated for my laptop, compilation process will simply destroy it, 4. microhs being small allows me to easily modify it |
2025-01-23 18:50:32 +0100 | Me-me | (~me-me@kc.randomserver.name) (Quit: Disconnecting on purpose.) |
2025-01-23 18:49:46 +0100 | target_i | (~target_i@user/target-i/x-6023099) target_i |
2025-01-23 18:49:26 +0100 | Guest6420 | vpan |
2025-01-23 18:48:58 +0100 | ColinRobinson | JuanDaugherty |
2025-01-23 18:48:55 +0100 | vpan | Guest6420 |
2025-01-23 18:48:31 +0100 | vpan | (~vpan@212.117.1.172) |
2025-01-23 18:48:25 +0100 | vpan | (~vpan@212.117.1.172) (Quit: Leaving.) |
2025-01-23 18:47:05 +0100 | dtman34 | (~dtman34@c-75-72-179-251.hsd1.mn.comcast.net) dtman34 |
2025-01-23 18:46:40 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Quit: = "") |
2025-01-23 18:46:14 +0100 | <__monty__> | homo: I think GHC keeps being brought up because most people see non-GHC Haskell as little more than a toy. |
2025-01-23 18:44:37 +0100 | <homo> | Bowuigi geekosaur generated code is considered binary, so no, that is not bootstrap from source, also I already stated earlier I have no interest touching ghc just like ghc developers have no interest in bootstrappability, ghc is haskell, but haskell is not ghc |
2025-01-23 18:43:20 +0100 | euleritian | (~euleritia@77.23.250.232) |
2025-01-23 18:43:12 +0100 | euleritian | (~euleritia@77.23.250.232) (Ping timeout: 265 seconds) |
2025-01-23 18:41:37 +0100 | dtman34 | (~dtman34@2601:447:d000:1f5e:db30:cdc7:b397:11f8) (Ping timeout: 248 seconds) |
2025-01-23 18:41:22 +0100 | Wstfgl0 | Me-me |
2025-01-23 18:41:17 +0100 | Me-me | (~me-me@user/me-me) (Ping timeout: 265 seconds) |
2025-01-23 18:40:59 +0100 | Wstfgl0 | (~me-me@kc.randomserver.name) |
2025-01-23 18:38:58 +0100 | <geekosaur> | (and tbh I think we're running out of folks who know how it works) |
2025-01-23 18:38:54 +0100 | j1n37 | (~j1n37@user/j1n37) j1n37 |
2025-01-23 18:38:46 +0100 | <geekosaur> | sadly I don't think the bootstrapping process is described anywhere, you would have to ask in #GHC:matrix.org |
2025-01-23 18:38:08 +0100 | <geekosaur> | via-C produces slow but portable ANSI C, which you can capture (-keep-hc-files, I think) and compile on another system |
2025-01-23 18:38:02 +0100 | hueso | (~root@user/hueso) hueso |
2025-01-23 18:36:46 +0100 | JuanDaugherty | ColinRobinson |
2025-01-23 18:35:14 +0100 | Guest4942 | vpan |
2025-01-23 18:35:04 +0100 | <haskellbridge> | <Bowuigi> homo would compiling GHC using GHC with the "-fvia-C" flag help with bootstrapping? https://downloads.haskell.org/ghc/latest/docs/users_guide/codegens.html |
2025-01-23 18:34:38 +0100 | hueso | (~root@user/hueso) (Quit: hueso) |
2025-01-23 18:34:02 +0100 | j1n37 | (~j1n37@user/j1n37) (Ping timeout: 265 seconds) |
2025-01-23 18:32:37 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 248 seconds) |
2025-01-23 18:31:45 +0100 | acidjnk | (~acidjnk@p200300d6e7283f96087c68b89a449bc9.dip0.t-ipconnect.de) acidjnk |
2025-01-23 18:31:19 +0100 | euleritian | (~euleritia@77.23.250.232) |
2025-01-23 18:31:03 +0100 | euleritian | (~euleritia@77.23.250.232) (Read error: Connection reset by peer) |
2025-01-23 18:28:10 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |