Google Git
Sign in
opensecura / 3p / lowrisc / opentitan / 6656e7f2b50d05a6ac36a8fa8f2426d18455255c
commit6656e7f2b50d05a6ac36a8fa8f2426d18455255c[log] [tgz]
authorRupert Swarbrick <rswarbrick@lowrisc.org>Wed Sep 23 17:09:49 2020 +0100
committerRupert Swarbrick <rswarbrick@gmail.com>Tue Sep 29 14:33:41 2020 +0100
tree0f2c1991c4d302aff06d3d9f31654b027d1ed585
parentb57138e1c27944af54e122b383ea44bc744aa3c6 [diff]
[verilator simutil] Add support for relative scope names to SVScoped

The SystemVerilog spec (1800-2017) doesn't seem to give any way to say
"start at the current scope and then follow the path ../../foo/bar".
Of course, it's not particularly difficult to implement once you've
decided on the semantics.

Here, we copy Python's import naming (they have the same dotted names,
so their solution should work quite well).

Suppose that the current scope is TOP.foo.bar.baz. Then SVScoped
should now resolve names as follows:

  TOP.qux -> TOP.qux
  qux     -> qux
  .       -> TOP.foo.bar.baz
  .a.b.c  -> TOP.foo.bar.baz.a.b.c
  .qux    -> TOP.foo.bar.baz.qux
  ..qux   -> TOP.foo.bar.qux
  ..      -> TOP.foo.bar
  ...     -> TOP.foo
  ....    -> TOP
  ......  -> TOP

Signed-off-by: Rupert Swarbrick <rswarbrick@lowrisc.org>
5 files changed
tree: 0f2c1991c4d302aff06d3d9f31654b027d1ed585
  1. .github/
  2. ci/
  3. doc/
  4. hw/
  5. site/
  6. sw/
  7. test/
  8. util/
  9. .clang-format
  10. .dockerignore
  11. .flake8
  12. .gitignore
  13. .style.yapf
  14. _index.md
  15. apt-requirements.txt
  16. azure-pipelines.yml
  17. check_tool_requirements.core
  18. CLA
  19. COMMITTERS
  20. CONTRIBUTING.md
  21. LICENSE
  22. meson.build
  23. meson_init.sh
  24. meson_options.txt
  25. python-requirements.txt
  26. README.md
  27. tool_requirements.py
  28. toolchain.txt
README.md

OpenTitan

OpenTitan logo

About the project

OpenTitan is an open source silicon Root of Trust (RoT) project. OpenTitan will make the silicon RoT design and implementation more transparent, trustworthy, and secure for enterprises, platform providers, and chip manufacturers. OpenTitan is administered by lowRISC CIC as a collaborative project to produce high quality, open IP for instantiation as a full-featured product. See the OpenTitan site and OpenTitan docs for more information about the project.

About this repository

This repository contains hardware, software and utilities written as part of the OpenTitan project. It is structured as monolithic repository, or “monorepo”, where all components live in one repository. It exists to enable collaboration across partners participating in the OpenTitan project.

Documentation

The project contains comprehensive documentation of all IPs and tools. You can access it online at docs.opentitan.org.

How to contribute

Have a look at CONTRIBUTING for guidelines on how to contribute code to this repository.

Licensing

Unless otherwise noted, everything in this repository is covered by the Apache License, Version 2.0 (see LICENSE for full text).