Newest at the top
| 2026-04-02 22:01:46 +0200 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-02 21:57:06 +0200 | Lord_of_Life_ | Lord_of_Life |
| 2026-04-02 21:54:27 +0200 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Ping timeout: 246 seconds) |
| 2026-04-02 21:54:18 +0200 | Lord_of_Life_ | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2026-04-02 21:50:33 +0200 | merijn | (~merijn@62.45.136.136) (Ping timeout: 248 seconds) |
| 2026-04-02 21:49:50 +0200 | califax | (~califax@user/califx) califx |
| 2026-04-02 21:49:36 +0200 | califax | (~califax@user/califx) (Remote host closed the connection) |
| 2026-04-02 21:46:23 +0200 | merijn | (~merijn@62.45.136.136) merijn |
| 2026-04-02 21:38:06 +0200 | zzz | (~zero@user/zero) (Ping timeout: 255 seconds) |
| 2026-04-02 21:37:33 +0200 | <davean> | tomsmeding: I know, its supported :) |
| 2026-04-02 21:37:14 +0200 | <davean> | Ah yah for anyone in that ecosystem. |
| 2026-04-02 21:37:12 +0200 | <tomsmeding> | davean: Futhark supports AMD GPUs :) |
| 2026-04-02 21:36:51 +0200 | <tomsmeding> | there's also Metal on the nice Apple chips |
| 2026-04-02 21:36:28 +0200 | <davean> | Its too bad, with the iGPUs and such floating around. |
| 2026-04-02 21:36:04 +0200 | <tomsmeding> | that depends on funding, I think |
| 2026-04-02 21:35:42 +0200 | <davean> | So no and never? |
| 2026-04-02 21:35:33 +0200 | <tomsmeding> | there's plans for one |
| 2026-04-02 21:35:23 +0200 | <davean> | tomsmeding: does it have an AMD backend these days that works? |
| 2026-04-02 21:33:48 +0200 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2026-04-02 21:30:23 +0200 | <tomsmeding> | in any case, the people hacking on accelerate are aware of all this, but there's little incentive in the academic system to spend the hours to fix it |
| 2026-04-02 21:29:41 +0200 | <tomsmeding> | yeah |
| 2026-04-02 21:29:36 +0200 | <davean> | and I don't mean that encuragingly. |
| 2026-04-02 21:29:33 +0200 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-02 21:29:32 +0200 | <tomsmeding> | davean: and very old stuff is more likely to still work than the fancy thing from 2 years ago |
| 2026-04-02 21:29:30 +0200 | <davean> | Ah yah if you're trying to hook it yourself instead of use the compiler which is what their spec actually is ... good luck! |
| 2026-04-02 21:28:58 +0200 | <tomsmeding> | doing this (instead of writing the CUDA glue code in C) was probably a mistake, and one that is in the plans of being fixed |
| 2026-04-02 21:28:40 +0200 | <tomsmeding> | if you try to bind CUDA functions from Haskell, you're more exposed to the function name shuffling they do under the hood |
| 2026-04-02 21:28:39 +0200 | <davean> | (I recently found out, because someone got me to fix the compile on an ancient game project) |
| 2026-04-02 21:28:13 +0200 | <davean> | There is something more |
| 2026-04-02 21:28:08 +0200 | <davean> | Hum, so CUDA software I have from 2008 still works fine. |
| 2026-04-02 21:27:40 +0200 | <tomsmeding> | the former seems to be fine so far |
| 2026-04-02 21:27:31 +0200 | <davean> | I get hesitant every time I consider designing something that relies on accelerate for this reason :) |
| 2026-04-02 21:27:18 +0200 | <tomsmeding> | Mostly depends on how backwards-compatible LLVM's IR format is, and how backwards-compatible CUDA turns out to be next year round |
| 2026-04-02 21:26:46 +0200 | <tomsmeding> | I dunno! |
| 2026-04-02 21:26:40 +0200 | <tomsmeding> | the CPU backend worked well enough for a long time already, by the way; it was the GPU backend that was unstable |
| 2026-04-02 21:26:39 +0200 | <davean> | Sure, the problem is will it work in a year? :) |
| 2026-04-02 21:26:22 +0200 | <tomsmeding> | well, I think it works well enough now for people to start testing it :) |
| 2026-04-02 21:26:13 +0200 | <tomsmeding> | right |
| 2026-04-02 21:26:02 +0200 | <davean> | the problem with that is it so often is broken no one can rely on it to start using it,. |
| 2026-04-02 21:26:01 +0200 | alter2000 | (~alter2000@user/alter2000) alter2000 |
| 2026-04-02 21:25:48 +0200 | <davean> | tomsmeding: I kinda assume for accelerate you need a lot of users to actually start testing well because of the complexity of the stack you sit on top of. |
| 2026-04-02 21:25:16 +0200 | <davean> | I was impacted a lot more by it just not having features. |
| 2026-04-02 21:25:16 +0200 | <tomsmeding> | davean: I can say with certainty that accelerate's current testing regime is beneath your standards, but at least it's slightly better than it was a few years ago |
| 2026-04-02 21:25:14 +0200 | tusko | (~uwu@user/tusko) tusko |
| 2026-04-02 21:25:01 +0200 | <davean> | Software was not good then, not at all, but its complexity vs. the effort put in was a bit more in balance. |
| 2026-04-02 21:24:55 +0200 | tusko | (~uwu@user/tusko) (Remote host closed the connection) |
| 2026-04-02 21:24:27 +0200 | <davean> | I probably am impacted by more software bugs each month now than I dealt with in the entir 2000-2005 period. |
| 2026-04-02 21:24:15 +0200 | alter2000 | (~alter2000@user/alter2000) (Ping timeout: 272 seconds) |
| 2026-04-02 21:22:42 +0200 | <EvanR> | I blame the compiler in the driver |
| 2026-04-02 21:21:33 +0200 | <davean> | Its a bit harder to test GPU compilers, esp since a lot of what you're debugging is the GPU stack |