Cursed project end of day 1: clinfo runs

[karolherbst@chaos.social]

Implemented basic control flow:

Pass 3280 Fails 142 Crashes 463

[karolherbst@chaos.social]

yeah soo.. is it day 5? I think it's day 5. Which is a bit weird because it feels like day 4. But maybe also because I started like almost at the end of the day? Maybe that doesn't count? Does it even matter? No, but anyway....

Status at the end of day 5:

Pass 3577 Fails 179 Crashes 129

What's missing?
- Image support
- Atomics
- Scratch
- Some math is failing validation.
- buffer synchronization issues, still.. I honestly don't know.
- optional gallium/nir stuff

[karolherbst@chaos.social]

I guess that's uhm... well... I guess?

[karolherbst@chaos.social]

oh shoo.. I'm like 10% slower than Nvidia's implementation 🙃

[karolherbst@chaos.social]

you all don't want to know the most cursed part about this 🙃

[oblomov@sociale.network]

@karolherbst we do actually, and you know we do 8-D

[karolherbst@chaos.social]

Pass 3769 Fails 112 Crashes 4 Timeouts 0

Something something atomics... and a few other random things, should be like 3 or 4 bugs in total...

[karolherbst@chaos.social]

okay... I found one of the atomic bugs.. it's when two kernels are launched back to back and apparently they can interact weirdly with each other. When I force a flush+wait between them those fails go away... curious

[karolherbst@chaos.social]

or maybe it's an ordering issue? mhh

[oblomov@sociale.network]

@karolherbst how would two kernels affect each other, unless they stomp on each other's memory? Did the hardware support concurrent kennel execution?