-
Notifications
You must be signed in to change notification settings - Fork 74
Conversation
chick
commented
Aug 21, 2019
- Create new VcsBackendAnnotation
- Create support utilities for Vcs building tools
- CopyVpiFiles move vpi and header files into place
- GenVcsVerilogHarness Compile stuff
- VcsAnnotations control behavior of the Vcs backend
- Create VcsBackend, a trivial sub-classing of VerilatorBackend
- Create VcsExecutive
- constructs VcsBackEnd requirements calls the constructor
- Create SimpleVcsTests
- Added String to Uniquify Verilator and Vcs Tests
- Test are ignored if VCS not present
- Create new VcsBackendAnnotation - Create support utilities for Vcs building tools - CopyVpiFiles move vpi and header files into place - GenVcsVerilogHarness Compile stuff - VcsAnnotations control behavior of the Vcs backend - Create VcsBackend, a trivial sub-classing of VerilatorBackend - Create VcsExecutive - constructs VcsBackEnd requirements calls the constructor - Create SimpleVcsTests - Added String to Uniquify Verilator and Vcs Tests
I am trying to find a setup where I can test this, will keep DO NOT MERGE label until then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor comments, looks fine otherwise. I mainly looked at the test code, we could probably significantly clean up the main implementation some other day.
Files.createFile(vpiTabFilePath) | ||
} catch { | ||
case _: FileAlreadyExistsException => | ||
System.out.format("") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wat
@@ -8,7 +8,7 @@ import chisel3.tester.internal.VerilatorBackendAnnotation | |||
import org.scalatest._ | |||
|
|||
class VerilatorBasicTests extends FlatSpec with ChiselScalatestTester with Matchers { | |||
behavior of "Testers2" | |||
behavior of "Testers2_Verilator" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe cleaner as "Testers2 with Verilator"? I don't think you need an underscore in quotes?
import org.scalatest._ | ||
|
||
class VcsBasicTests extends FlatSpec with ChiselScalatestTester with Matchers { | ||
behavior of "Testers2_Vcs" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto, "testesr2 with vcs"?
} | ||
} | ||
|
||
it should "fail on poking outputs" in { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems more like a testers2 infrastructure exception, not sure if it belongs in a VCS test?
} | ||
} | ||
|
||
it should "fail with user-defined message" in { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto, is this VCS-specific? I don't think so, or at least the control paths are redundant with the fail-on-expect simple case?
- Fixed CopyVpiFiles - looks like this might fail if early file was there but a late one wasn't - this code came from chisel-testers - Fix top level test names - behavior of "Testers2 with Vcs" - behavior of "Testers2 with Verilator" - Shortened VCS to just see if a simple circuit will build and simulate. - in long run we still need mechanism to run an arbitrary test with arbitrary backend
Hello @chick. what’s the currently progress on vcs porting to tester2. |
- Create new VcsBackendAnnotation - Create support utilities for Vcs building tools - CopyVpiFiles move vpi and header files into place - GenVcsVerilogHarness Compile stuff - VcsAnnotations control behavior of the Vcs backend - Create VcsBackend, a trivial sub-classing of VerilatorBackend - Create VcsExecutive - constructs VcsBackEnd requirements calls the constructor - Create SimpleVcsTests - Added String to Uniquify Verilator and Vcs Tests - Suppress VCS tests if VCS not present in path - Updates to PR #58 - Fixed CopyVpiFiles - looks like this might fail if early file was there but a late one wasn't - this code came from chisel-testers - Fix top level test names - behavior of "Testers2 with Vcs" - behavior of "Testers2 with Verilator" - Shortened VCS to just see if a simple circuit will build and simulate. - in long run we still need mechanism to run an arbitrary test with arbitrary backend
…d-vcs-backend-support # Conflicts: # src/main/scala/chiseltest/internal/Testers2.scala
- Create new VcsBackendAnnotation - Create support utilities for Vcs building tools - CopyVpiFiles move vpi and header files into place - GenVcsVerilogHarness Compile stuff - VcsAnnotations control behavior of the Vcs backend - Create VcsBackend, a trivial sub-classing of VerilatorBackend - Create VcsExecutive - constructs VcsBackEnd requirements calls the constructor - Create SimpleVcsTests - Added String to Uniquify Verilator and Vcs Tests - Suppress VCS tests if VCS not present in path - Updates to PR #58 - Fixed CopyVpiFiles - looks like this might fail if early file was there but a late one wasn't - this code came from chisel-testers - Fix top level test names - behavior of "Testers2 with Vcs" - behavior of "Testers2 with Verilator" - Shortened VCS to just see if a simple circuit will build and simulate. - in long run we still need mechanism to run an arbitrary test with arbitrary backend - Create new VcsBackendAnnotation - Create support utilities for Vcs building tools - CopyVpiFiles move vpi and header files into place - GenVcsVerilogHarness Compile stuff - VcsAnnotations control behavior of the Vcs backend - Create VcsBackend, a trivial sub-classing of VerilatorBackend - Create VcsExecutive - constructs VcsBackEnd requirements calls the constructor - Create SimpleVcsTests - Added String to Uniquify Verilator and Vcs Tests - Fixed CopyVpiFiles - looks like this might fail if early file was there but a late one wasn't - this code came from chisel-testers - Fix top level test names - behavior of "Testers2 with Vcs" - behavior of "Testers2 with Verilator" - Shortened VCS to just see if a simple circuit will build and simulate. - in long run we still need mechanism to run an arbitrary test with arbitrary backend merged latest version of master then did lots and lots of cleanup
This should not be merged |
- Create new VcsBackendAnnotation - Create support utilities for Vcs building tools - CopyVpiFiles move vpi and header files into place - GenVcsVerilogHarness Compile stuff - VcsAnnotations control behavior of the Vcs backend - Create VcsBackend, a trivial sub-classing of VerilatorBackend - Create VcsExecutive - constructs VcsBackEnd requirements calls the constructor - Create SimpleVcsTests - Added String to Uniquify Verilator and Vcs Tests - Suppress VCS tests if VCS not present in path - Updates to PR #58 - Fixed CopyVpiFiles - looks like this might fail if early file was there but a late one wasn't - this code came from chisel-testers - Fix top level test names - behavior of "Testers2 with Vcs" - behavior of "Testers2 with Verilator" - Shortened VCS to just see if a simple circuit will build and simulate. - in long run we still need mechanism to run an arbitrary test with arbitrary backend - Create new VcsBackendAnnotation - Create support utilities for Vcs building tools - CopyVpiFiles move vpi and header files into place - GenVcsVerilogHarness Compile stuff - VcsAnnotations control behavior of the Vcs backend - Create VcsBackend, a trivial sub-classing of VerilatorBackend - Create VcsExecutive - constructs VcsBackEnd requirements calls the constructor - Create SimpleVcsTests - Added String to Uniquify Verilator and Vcs Tests - Fixed CopyVpiFiles - looks like this might fail if early file was there but a late one wasn't - this code came from chisel-testers - Fix top level test names - behavior of "Testers2 with Vcs" - behavior of "Testers2 with Verilator" - Shortened VCS to just see if a simple circuit will build and simulate. - in long run we still need mechanism to run an arbitrary test with arbitrary backend merged latest version of master then did lots and lots of cleanup