big awoo notationI want to see if the thoughts of others align with mine.
An FPGA toolchain should optimise for:
An FPGA toolchain should optimise for:
highest worst-case Fmax
highest average Fmax
highest best-case Fmax
Poll ended at .
Luke Wren@lofty Depends how many parallel jobs I am allowed to submit to get that golden seed 😅
@wren6991 I'm computing distributions of 100 runs, so
@lofty If I'm comparing RTL changes for fmax then I'll usually do ~100 runs and take the median. Seems reasonable because 8 runs aiming for median frequency should have only a 0.4% chance of all failing. Most client machines have 8 parallel threads of execution available these days.
I don't particularly care about the mean because if I get a worst-case result then you can bet I'm re-rolling, so the tail values don't matter.
I don't think it's *good* that seed sweeping is the optimal way of using the tools, but the fact is it reduces variance as well as increasing expected fmax.
@lofty Also bear in mind my comparison point here is Vivado which has a >> 0.4% chance of just segfaulting for no apparent reason, so I find that kind of probability acceptable
mei
Matteê™® Italia@mei @lofty @wren6991 on one end I'm like "niiiice, but well, this can be improved, the queue can be made lock free, and we can drop the mutex from the initialization of the forwarded symbols through careful use of atomics; also, we may improve resilience by adjusting the return value to have some extra slack even at the start"; on the other hand I'm like NO THIS IS BAD LET IT BE SLOW
@cvtsi2sd serialising all the calls to free might also be helping with race conditions
Michał Trojnara 
Mae