First resultMXCore
Arithmetic is the design choice.
pre spin changes the datapath arithmetic at RTL and proves the change with a formal error bound.
Changed the arithmetic. Timing still met. No measurable perplexity change.
How it works
RTL in, RTL out. In between, a bound you can check.
-
01
Your RTL
Send the datapath as RTL. A throwaway block is a fine place to start.
-
02
A formal bound
We change the arithmetic at RTL and prove the change with a formal error bound.
-
03
Back to you
Optimised RTL, a bit-exact Python model and test vectors. The error bound is yours to check.
The result
Timing met. Area and power down.
| Measure | Change | Scope |
|---|---|---|
| Area | −9.7% | Whole MXCore |
| Power | −6.0% | MXFP8 engine |
| Perplexity | −0.005% | No measurable change |
| Timing | Met | MXCore |
N=1.
One design so far, MXCore. Yours could be N=2.
Notes
-
Where the error bound comes from
-
Bit-exact, and how we check it
-
MXCore, before and after
Team
“We” is two people.
-
Tom de Vrieze
Founder
tom@prespin.com -
Leo Strijbos
Founder
leo@prespin.com
Start with a throwaway block of RTL.
Or a conversation about your flow. Confidentiality can be agreed upfront.