-
Updated
Apr 14, 2021 - Haskell
systemverilog
Here are 355 public repositories matching this topic...
-
Updated
Jul 7, 2020 - SystemVerilog
Input test case
Any sv file.
Describe what is wrong or missing
As far as I can tell, the verible-verilog-kythe-extractor tool cannot directly write its output into a file.
The issue is that it force having a potentially huge buffer in memory.
It would be nice to have the capability to output the result of the kythe extraction directly to an output file without having to rely on
-
Updated
Apr 13, 2021 - Verilog
-
Updated
Apr 9, 2021 - Python
-
Updated
Apr 15, 2021 - SystemVerilog
-
Updated
Mar 19, 2021 - C++
-
Updated
Mar 5, 2021 - Rust
-
Updated
Apr 14, 2021 - Haskell
-
Updated
Apr 11, 2021 - C++
-
Updated
Nov 25, 2019 - SystemVerilog
-
Updated
Apr 8, 2021 - Python
-
Updated
Oct 19, 2020 - Verilog
When running the regression, the resulting logs seem to end up in third_party/tests/$TEST/.... This of course is not unnoticed by git, so a git status shows a ton of non-added new files added.
To reproduce:
make
make regression
git status # observe all the filesBuild or test artifacts should never clutter the rest of the code-base (we should regard them as read-only in
-
Updated
Apr 4, 2021 - TypeScript
-
Updated
Apr 12, 2021 - SystemVerilog
-
Updated
Apr 12, 2021 - Python
-
Updated
Apr 14, 2021 - JavaScript
- AxProt[0]
- 0: Unprivileged access
- 1: Privileged access
- AxProt[1]
- Secure access
- Non-secure access
- AxProt[2]
- Data access
- Instruction access
-
Updated
Mar 13, 2021 - Ruby
-
Updated
Oct 28, 2019 - Python
-
Updated
Sep 2, 2020 - SystemVerilog
-
Updated
Mar 10, 2018 - SystemVerilog
Improve this page
Add a description, image, and links to the systemverilog topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the systemverilog topic, visit your repo's landing page and select "manage topics."

If you speak another language, I would appreciate your help in translating the
README.md.For tables, checklists, or other data that might change, please indicate that that information is in the main README. Otherwise every change to the main README will need to be replicated to the other READMEs.
^ I've tried to do this a bit in the French README. The only thing you need to replicate when