News for hackers. Stuff that matters.
Re:BOOM v2: an open-source out-of-order RISC-V core by JoshTriplett on Tuesday September 26, 2017 @08:01PM (#15343737)
Out-of-order execution isn't only about instruction order, and static scheduling can't give you everything. One execution of a given chunk of code might have something in cache, another execution of that same code might not. One execution might consistently take one branch, another might consistently take another, because it varies based on workload.

Out-of-order execution helps with things like "I don't have the memory fetch done yet, but let's make a reasonable assumption and then speculatively do lots more that doesn't depend on that fetch".

Re:BOOM v2: an open-source out-of-order RISC-V core by deepnotderp on Wednesday September 27, 2017 @01:05AM (#15345058)
While true in principle, in practice the majority (~88%) of the gains of OoO come not from reactions to dynamic events (e.g. caches misses) but rather from schedules.

This is relatively recent research, and definitely against the common grain. See Daniel McFarlin's work at CMU (https://dl.acm.org/citation.cfm?id=2499368.2451143)

Re:BOOM v2: an open-source out-of-order RISC-V core by dnautics on Tuesday September 26, 2017 @08:08PM (#15343787)
thanks! Cache miss latency! I forgot about that.
Re:BOOM v2: an open-source out-of-order RISC-V core by ant6n on Wednesday September 27, 2017 @12:45AM (#15344998)
It means

   load [rp1] -> r1
   inc  r1
   load [rp2] -> r2
   inc  r2
may execute in a different order for every execution.