Visible to Intel only — GUID: mmi1469133916284
Ixiasoft
1.1. Compilation Overview
1.2. Using the Compilation Dashboard
1.3. Design Netlist Infrastructure
1.4. Using the Node Finder
1.5. Precompiled Component (PCC) Generation Flow
1.6. Analysis & Elaboration Flow
1.7. Design Synthesis
1.8. Design Place and Route
1.9. Incremental Optimization Flow
1.10. Fast Forward Compilation Flow
1.11. Full Compilation Flow
1.12. Compilation Monitoring Mode
1.13. Exporting Compilation Results
1.14. Integrating Other EDA Tools
1.15. Compiler Optimization Techniques
1.16. Synthesis Language Support
1.17. Synthesis Settings Reference
1.18. Fitter Settings Reference
1.19. Design Compilation Revision History
1.7.3.1. Registering the SDC-on-RTL SDC File
1.7.3.2. Applying the SDC-on-RTL Constraints
1.7.3.3. Inspecting SDC-on-RTL Constraints
1.7.3.4. Creating Constraints in SDC-on-RTL SDC Files
1.7.3.5. Using Entity-Based SDC-on-RTL Constraints
1.7.3.6. Types of SDC Files Used in the Quartus® Prime Software
1.7.3.7. Example: Using SDC-on-RTL Features
1.13.1. Exporting a Version-Compatible Compilation Database
1.13.2. Importing a Version-Compatible Compilation Database
1.13.3. Creating a Design Partition
1.13.4. Exporting a Design Partition
1.13.5. Reusing a Design Partition
1.13.6. Viewing Quartus Database File Information
1.13.7. Clearing Compilation Results
2.1. Factors Affecting Compilation Results
2.2. Strategies to Reduce the Overall Compilation Time
2.3. Reducing Synthesis Time and Synthesis Netlist Optimization Time
2.4. Reducing Placement Time
2.5. Reducing Routing Time
2.6. Reducing Static Timing Analysis Time
2.7. Setting Process Priority
2.8. Reducing Compilation Time Revision History
Visible to Intel only — GUID: mmi1469133916284
Ixiasoft
1.9. Incremental Optimization Flow
The Quartus® Prime Pro Edition software supports incremental optimization at each stage of design compilation. In incremental optimization, you run and optimize each compilation stage independently before running the next compilation module in sequence. The Compiler preserves the results of each stage as a snapshot for analysis. When you make changes to your design or constraints, the Compiler only runs stages impacted by the change. Following synthesis or any Fitter stage, you can view results and perform timing analysis; modify design RTL or Compiler settings as needed; and then re-run synthesis or the Fitter and evaluate the results of these changes. Repeat this process until the module performance meets requirements. This flow maximizes the results at each stage without waiting for full compilation results.
Figure 80. Incremental Optimization Flow
Fitter Stage | Incremental Optimization |
---|---|
Plan | After this stage, you can run post-Plan timing analysis to verify timing constraints, and validate cross-clock timing windows. View the placement and properties of the periphery (I/O). |
Place | After this stage, validate resource and logic utilization in the Compilation Reports, and review placement of design elements in the Chip Planner. |
Route | After this stage, perform detailed setup and hold timing closure in the Timing Analyzer, and view routing congestion in the Chip Planner. |
Retime | After this stage, review the Retiming results in the Fitter report and correct any restrictions limiting further retiming optimization. |
Note: The Compiler saves the planned, placed, routed, and retimed snapshots during full compilation only if you turn on Enable Intermediate Fitter Snapshots (Assignments > Settings > Compiler Settings). You can also run any intermediate Fitter stage independently to generate the snapshot for that stage.