-
Notifications
You must be signed in to change notification settings - Fork 146
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix linking to find VPI files in the Verilog path
Previously, the linking stage assumed that VPI wrapper files were in the vdir or (if no vdir) the current directory (where BSC is invoked). This probably explains why the compile stage had been changed to put the VPI wrappers in the current directory (see previous commit, which reverts that change). BSC needs to support linking where VPI wrappers are found in various directories -- both because of the change to the compile stage (to put the VPI wrappers in the various source directories) but also because the files may not have been compiled with the same vdir. Specificaly, users will want to compile files into a library, that can be used with multiple designs; those files should be able to sit in their own directory tree. If the library contains imported C functions, then VPI wrapper files will be in the directory tree, and the BSC link stage will need to be able to find them. Now that the compile stage is putting VPI wrapper files in the same location with Verilog files, the linking stage can use the Verilog search path to find them. This makes that change and adds tests.
- Loading branch information
Showing
5 changed files
with
94 additions
and
36 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters