[rtl] Convert some non-ANSI parameters to localparams

It turns out that there's a slightly obscure corner of the SV spec
that says that if you have a module like this:

  module foo #(
    parameter int Foo = 0
  ) (
    // ...
  );
    parameter int Bar = 1;
    // ...

  endmodule

then Bar essentially becomes a localparam: the presence of the ANSI
parameter list means that all non-ANSI parameters get treated as
localparams. Furthermore, some tools (Vivado, at least) warn when this
happens.

Convert these parameters to localparams, which is how they will behave
anyway.

This commit switches all occurrences that I found with

    git ls-files -- '*.sv' | \
      grep -v vendor | \
      xargs -n1 awk '\
        /module.*#\(/ {if(x==0) x=1} \
        /\)\s*\(/ {if(x==1) x=2;} \
        /^[^/]*parameter/ {\
          if(x==2) printf("%s:%s: %s\n", FILENAME, FNR, $0);\
        }'

(Note: there are a few false positives that this script finds in
aes_sbox_dom.sv, which has more than one module in the file).

Signed-off-by: Rupert Swarbrick <rswarbrick@lowrisc.org>
6 files changed
tree: 9fc3d4b1afc83d522f6362d9b760790910e47806
  1. .github/
  2. ci/
  3. doc/
  4. hw/
  5. rules/
  6. site/
  7. sw/
  8. test/
  9. third_party/
  10. util/
  11. .bazelignore
  12. .bazelrc
  13. .bazelversion
  14. .clang-format
  15. .dockerignore
  16. .flake8
  17. .gitignore
  18. .style.yapf
  19. .svlint.toml
  20. .svls.toml
  21. _index.md
  22. apt-requirements.txt
  23. azure-pipelines.yml
  24. BUILD.bazel
  25. check_tool_requirements.core
  26. CLA
  27. COMMITTERS
  28. CONTRIBUTING.md
  29. LICENSE
  30. meson-config.txt
  31. meson.build
  32. meson_init.sh
  33. meson_options.txt
  34. python-requirements.txt
  35. README.md
  36. tool_requirements.py
  37. toolchain.txt
  38. topgen-reg-only.core
  39. topgen.core
  40. WORKSPACE
  41. yum-requirements.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]({{< relref “CONTRIBUTING.md” >}}) and our documentation on project organization and processes 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).