| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| | |
RTL contract violations and C++ contract violations are different:
the former depend on the netlist and will never violate memory safety
whereas the latter may. When loading a CXXRTL simulation into another
process, RTL contract violations should generally not crash it, while
C++ contract violations should.
|
| |\ \
| | |
| | | |
cxxrtl: fix crashes caused by a floating or constant clock input
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
E.g. in:
module test;
wire clk = 0;
reg data;
always @(posedge clk)
data <= 0;
endmodule
|
| |/
|
|
|
|
|
|
|
|
|
| |
Although it is always possible to destroy and recreate the design to
simulate a power-on reset, this has two drawbacks:
* Black boxes are also destroyed and recreated, which causes them
to reacquire their resources, which might be costly and/or erase
important state.
* Pointers into the design are invalidated and have to be acquired
again, which is costly and might be very inconvenient if they are
captured elsewhere (especially through the C API).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In most cases, a CXXRTL simulation would use a top module, either
because this module serves as an entry point to the CXXRTL C API,
or because the outputs of a top module are unbuffered, improving
performance. Taking this into account, the CXXRTL backend now runs
`hierarchy -auto-top` if there is no top module. For the few cases
where this behavior is unwanted, it now accepts a `-nohierarchy`
option.
Fixes #2373.
|
| |
|
|
| |
Fixes #2129.
|
| |
|
|
| |
Fixes #2374.
|
| |
|
|
|
|
| |
This can be useful to determine whether the wire should be a part of
a design checkpoint, whether it can be used to override design state,
and whether driving it may cause a conflict.
|
| |
|
|
|
|
|
|
|
|
| |
Before this commit, the meaning of "sync def" included some flip-flop
cells but not others. There was no actual reason for this; it was
just poorly defined.
After this commit, a "sync def" means that a wire holds design state
because it is connected directly to a flip-flop output, and may never
be unbuffered. This is not affected by presence of async inputs.
|
| |
|
|
|
|
| |
This can be useful to distinguish e.g. a combinatorially driven wire
with type `CXXRTL_VALUE` from a module input with the same type, as
well as general introspection.
|
| | |
|
| |
|
|
| |
This bug was hidden if a header was generated.
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
cxxrtl: don't compute vital values in log_assert()
|
| | |
| |
| |
| |
| |
| | |
This breaks NDEBUG builds.
Fixes #2166.
|
| |\ \
| | |
| | | |
cxxrtl: restrict the debug info of a blackbox to its ports.
|
| | |/ |
|
| |/ |
|
| |\
| |
| | |
cxxrtl: handle multipart signals
|
| | |
| |
| |
| | |
This avoids losing design visibility when using the `splitnets` pass.
|
| | | |
|
| | |
| |
| |
| |
| | |
On Minerva, this improves runtime by around 10%, mostly by ensuring
that the logic driving FFs is packed into edge conditionals.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Without unbuffering output wires of, at least, toplevel modules, it
is not possible to have most designs that rely on IO via toplevel
ports (as opposed to using exclusively blackboxes) converge within
one delta cycle. That seriously impairs the performance of CXXRTL.
This commit avoids unbuffering outputs of all modules solely so that
in future, CXXRTL could gain fully separate compilation, and not for
any present technical reason.
|
| |/
|
|
| |
This also fixes an edge case with (*keep*) input ports.
|
| |\
| |
| | |
cxxrtl: various compiler compatibility fixes
|
| | |
| |
| |
| | |
This is necessary to be able to build CXXRTL models via yosys-config.
|
| |/
|
|
|
|
|
| |
With this change, it is easier to see which signals carry state (only
wire<>s appear as `reg` in VCD files) and to construct a minimal
checkpoint (CXXRTL_WIRE debug items represent the canonical smallest
set of state required to fully reconstruct the simulation).
|
| |
|
|
|
|
|
| |
Although logically two separate steps, these were treated as one for
historic reasons. Splitting the two makes it possible to have designs
that are only 2× slower than fastest possible (and are without extra
delta cycles) that allow probing all public wires.
|
| |
|
|
|
|
|
|
|
|
|
| |
Historically, elision was implemented before localization, so levels
with elision are lower than corresponding levels with localization.
This is unfortunate for two reasons:
1. Elision is a logical subset of localization, since it equals to
not giving a name to a temporary.
2. "Localize" currently actually means "unbuffer and localize",
and it would be useful to split those steps (at least for
public wires) for improved design visibility.
|
| |
|
|
|
|
|
|
| |
Although these options can be thought of as optimizations, they are
essentially orthogonal to the core of -O, which is managing signal
buffering and scope. Going from -O4 to -O2 means going from limited
to complete design visibility, yet in both cases proc and flatten
are desirable.
|
| | |
|
| |
|
|
|
|
|
|
| |
Before this commit, Verilog expressions like `x && 1` would result in
references to `logic_and_us` in generated CXXRTL code, which would
not compile. After this commit, since cells like that actually behave
the same regardless of signedness attributes, the signedness is
ignored, which also reduces the template instantiation pressure.
|
| |
|
|
|
| |
The CXXRTL code that handled the `hdlname` attribute implemented
outdated semantics.
|
| |
|
|
|
|
|
|
|
| |
Constant wires can represent a significant chunk of the design in
generic designs or after optimization. Emitting them in VCD files
significantly improves usability because gtkwave removes all traces
that are not present in the VCD file after reload, and iterative
development suffers if switching a varying signal to a constant
disrupts the workflow.
|
| |
|
|
|
|
|
| |
Alias wires can represent a significant chunk of the design in highly
hierarchical designs; in Minerva SRAM, there are 273 member wires and
527 alias wires. Showing them in every hierarchy level significantly
improves usability.
|
| | |
|
| | |
|
|
|
To avoid confusion with the C++ source files that are a part of
the simulation itself and not a part of Yosys build.
|
