Difference between revisions of "Notes on analysis"
From Verific Design Automation FAQ
(Created page with "This is a place holder for notes regarding analysis of System Verilog designs. Can I use veri_file::Analyze to read SV input files one by one? Yes. But if you have multiple...") |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | First, please read this article: [[Defined macros become undefined - MFCU vs SFCU]]. | |
| − | Can I use veri_file::Analyze to read | + | ''>> Can I use veri_file::Analyze) to read System Verilog input files one by one, all of them belonging to one compilation unit?'' |
Yes. But if you have multiple files, it’s better to use veri_file::AnalyzeMultipleFiles(). | Yes. But if you have multiple files, it’s better to use veri_file::AnalyzeMultipleFiles(). | ||
| Line 7: | Line 7: | ||
veri_file::AnalyzeMultipleFiles(), besides analyzing each files, also: | veri_file::AnalyzeMultipleFiles(), besides analyzing each files, also: | ||
| − | + | * opens and ends the compilation unit | |
| − | + | * processes –v and –y options | |
| − | + | * removes include directories | |
| − | + | * processes root module | |
| − | + | * undefines user-defined macros | |
| − | + | * resets compile directives (e.g. `default_nettype, `timescale) | |
| − | If you use veri_file::Analyze() to analyze files one by one | + | If you use veri_file::Analyze() to analyze files one by one, you’ll need to call these APIs to complete the analysis before starting any other operations: |
| − | + | * veri_file::ProcessUserLibraries() | |
| − | + | * veri_file::RemoveAllIncludeDirs() | |
| − | + | * veri_file::EndCompilationUnit() | |
Revision as of 12:03, 9 July 2021
First, please read this article: Defined macros become undefined - MFCU vs SFCU.
>> Can I use veri_file::Analyze) to read System Verilog input files one by one, all of them belonging to one compilation unit?
Yes. But if you have multiple files, it’s better to use veri_file::AnalyzeMultipleFiles().
veri_file::AnalyzeMultipleFiles(), besides analyzing each files, also:
- opens and ends the compilation unit
- processes –v and –y options
- removes include directories
- processes root module
- undefines user-defined macros
- resets compile directives (e.g. `default_nettype, `timescale)
If you use veri_file::Analyze() to analyze files one by one, you’ll need to call these APIs to complete the analysis before starting any other operations:
- veri_file::ProcessUserLibraries()
- veri_file::RemoveAllIncludeDirs()
- veri_file::EndCompilationUnit()
