Veripool

08/31/2019

11:24 PM Verilator Development: RE: Building Verilator with Bazel

Quick update for anyone who's come across this thread: I've improved the Bazel rules such that they no longer require...

05/15/2019

12:52 AM Verilator Issue #1440: V3Ast.cpp gives warning with -Winvalid-noreturn

Awesome, thanks for the clarification!

05/14/2019

10:17 PM Verilator Issue #1440 (Closed): V3Ast.cpp gives warning with -Winvalid-noreturn

Compiling src/V3Ast.cpp produces the following warning when compiled with -Winvalid-noreturn (Apple LLVM version 10.0...

10/02/2018

06:51 PM Verilator Development: RE: Building Verilator with Bazel

Your solution breaks in an identical way if /* verilator public */ is used.

09/28/2018

06:44 PM Verilator Development: RE: Building Verilator with Bazel

Assuming you're talking about Verilog parameters changing the hierarchy, would that not be true for your proposal as ...

01:13 AM Verilator Development: RE: Building Verilator with Bazel

> If a public file or hierarchy changes you must edit your rules by definition of needing those headers, but no other...

09/27/2018

09:18 PM Verilator Development: RE: Building Verilator with Bazel

Suppose I have the file following file top.sv compiled with "--cc top.sv --top-module top":...

09/26/2018

09:23 PM Verilator Development: RE: Building Verilator with Bazel

> The case you describe is protected by erroring (outside Verilator) if the repository ever attempts to contains two ...

08:00 AM Verilator Development: RE: Building Verilator with Bazel

> Our and "typical" build system pass Verilator only the top module name and appropriate flags, and verilator figures...

09/25/2018

11:16 PM Verilator Development: RE: Building Verilator with Bazel

> Yes. The build systems I've used to date always would automatically use the dependencies Verilator/the simulator fo...