What would be workflow for creating and installing external haskell packages? I am running snap from release 1.2. I used to work with cabal in past, but I am out of loop on current packet management in new environment.

Any pointers would be much appreciated.

Example formatter output of reduced test case:

task t;
  a_pkg::foo #(x)::func();
endtask

Should be:

task t;
  a_pkg::foo#(x)::func();
endtask

Here is a simple example for Vivado.

https://github.com/SymbiFlow/fpga-tool-perf/blob/f8438d0447ae808fd1434073b037fa30b274c423/fpgaperf.py#L444-L506

    def vivado_resources(self):
        report_path = self.out_dir + "/" + self.project_name + ".runs/impl_1/top_utilization_placed.rpt"
        with open(report_path, 'r') as fp:
            report_data = fp.read()
            repo

Author Name: Enze Chi
Original Redmine Issue: 1495 from https://www.veripool.org

With verilog-mode from master branch (be9b5af)

I have 3 expression as below, after press , I got wrong alignment for the example code as below:

     startc_c         <= (valid && (state == THE_START));
     end_c             <= (valid && (state == THE_END));
     valid_c          

Verilator should only run on Verilog-HDL with proper Verilog file extensions.

maybe a

verilog.lint.include : [".sv", ".v"] //Verilog HDL/SystemVerilog configuration setting

Add command line option, to enable the user to choose which builder he/she wants to use. Suggestion:
--builder BUILDER specify the builded to be used

By adding it, it would allow:

1. Users to actively choose the builder the way to use, without any code change (e.g. editing hdl_checker/builder_utils.py).
2. to separate use cases and make it easier to track bugs that may arise.

We need more tests for this chapter, examples:

next_id = ++id;

or

b = (a+=1);

Ref: #609

Surelog should publish documentation on ReadTheDocs like all good packages.

See https://docs.readthedocs.io/en/stable/ on how to get started.

The docs should be published at https://surelog.readthedocs.io/

• AxProt[0]
  • 0: Unprivileged access
  • 1: Privileged access
• AxProt[1]
  • Secure access
  • Non-secure access
• AxProt[2]
  • Data access
  • Instruction access