←back to thread

Condor's Cuzco RISC-V Core at Hot Chips 2025

(chipsandcheese.com)
154 points rbanffy | 1 comments | 30 Aug 25 14:18 UTC | HN request time: 0s | source
Show context
bee_rider ◴[30 Aug 25 15:20 UTC] No.45075394[source]▶
The static schedule part seems really interesting. They note that it only works for some instructions, but I wonder if it would be possible to have a compiler report “this section of the code can be statically scheduled.” In that case, could this have a benefit for real-time operation? Or maybe some specialized partially real-time application—mark a segment of the program as desiring static scheduling, and don’t allow memory loads, etc, inside there.
replies(4): >>45075641 #>>45075901 #>>45078349 #>>45087597 #
1. clamchowder ◴[30 Aug 25 21:58 UTC] No.45078349[source]▶
(author here) they try for all instructions, just that it's a prediction w/replay because inevitably some instructions like memory loads are variable latency. It's not like Nvidia where fixed latency instructions are statically scheduled, then memory loads/other variable latency stuff is handled dynamically via scoreboarding.