The Vivado tools support a pushbutton flow, as well as the sweeping of strategies. Runs can be set per your requirements and can be launched in parallel or sequentially, based on the number of compute resources available.
In general, AMD recommends running the Vivado tools with the default synthesis and implementation strategies. These provide the best balance between performance and runtime and are in most cases sufficient to meet the requested performance target.
The following table lists the Quartus Prime compiler optimization modes and the equivalent Vivado Design Suite implementation strategies.
| Quartus Prime Compiler Optimization Mode | Vivado Implementation Strategy |
|---|---|
| Balanced (normal flow) | Vivado implementation defaults |
| Performance (high effort – increases runtime) |
Performance_Explore Performance_ExplorePostRoutePhysOpt |
| Performance (aggressive – increases runtime and area) | |
| Power (high effort – increases runtime) | Power_DefaultOpt |
| Power (aggressive – increases runtime, reduces performance) | |
| Area (Aggressive – reduces performance) | Area_Explore |
The following table lists the Quartus Prime register optimizations and the equivalent Vivado Design Suite implementation settings.
| Quartus Prime Prevent Register Optimization | Vivado Implementation Options |
|---|---|
| Prevent register merging |
|
| Prevent register duplication | Disable phys_opt_design
|
| Prevent register re-timing |
|