mirror of
https://github.com/YosysHQ/yosys
synced 2025-04-05 17:14:08 +00:00
fe74b0cd95
This change set contains a number of bug fixes and improvements related to
scoping and resolution in generate and procedural blocks. While many of the
frontend changes are interdependent, it may be possible bring the techmap
changes in under a separate PR.
Declarations within unnamed generate blocks previously encountered issues
because the data declarations were left un-prefixed, breaking proper scoping.
The LRM outlines behavior for generating names for unnamed generate blocks. The
original goal was to add this implicit labelling, but doing so exposed a number
of issues downstream. Additional testing highlighted other closely related scope
resolution issues, which have been fixed. This change also adds support for
block item declarations within unnamed blocks in SystemVerilog mode.
1. Unlabled generate blocks are now implicitly named according to the LRM in
`label_genblks`, which is invoked at the beginning of module elaboration
2. The Verilog parser no longer wraps explicitly named generate blocks in a
synthetic unnamed generate block to avoid creating extra hierarchy levels
where they should not exist
3. The techmap phase now allows special control identifiers to be used outside
of the topmost scope, which is necessary because such wires and cells often
appear in unlabeled generate blocks, which now prefix the declarations within
4. Some techlibs required modifications because they relied on the previous
invalid scope resolution behavior
5. `expand_genblock` has been simplified, now only expanding the outermost
scope, completely deferring the inspection and elaboration of nested scopes;
names are now resolved by looking in the innermost scope and stepping outward
6. Loop variables now always become localparams during unrolling, allowing them
to be resolved and shadowed like any other identifier
7. Identifiers in synthetic function call scopes are now prefixed and resolved
in largely the same manner as other blocks
before: `$func$\func_01$tests/simple/scopes.blk.v:60$5$\blk\x`
after: `\func_01$func$tests/simple/scopes.v:60$5.blk.x`
8. Support identifiers referencing a local generate scope nested more
than 1 level deep, i.e. `B.C.x` while within generate scope `A`, or using a
prefix of a current or parent scope, i.e. `B.C.D.x` while in `A.B`, `A.B.C`,
or `A.B.C.D`
9. Variables can now be declared within unnamed blocks in SystemVerilog mode
Addresses the following issues: 656, 2423, 2493
40 lines
1.2 KiB
Systemverilog
40 lines
1.2 KiB
Systemverilog
// This test is taken directly from Section 27.6 of IEEE 1800-2017
|
|
|
|
module top;
|
|
parameter genblk2 = 0;
|
|
genvar i;
|
|
|
|
// The following generate block is implicitly named genblk1
|
|
|
|
if (genblk2) logic a; // top.genblk1.a
|
|
else logic b; // top.genblk1.b
|
|
|
|
// The following generate block is implicitly named genblk02
|
|
// as genblk2 is already a declared identifier
|
|
|
|
if (genblk2) logic a; // top.genblk02.a
|
|
else logic b; // top.genblk02.b
|
|
|
|
// The following generate block would have been named genblk3
|
|
// but is explicitly named g1
|
|
|
|
for (i = 0; i < 1; i = i + 1) begin : g1 // block name
|
|
// The following generate block is implicitly named genblk1
|
|
// as the first nested scope inside g1
|
|
if (1) logic a; // top.g1[0].genblk1.a
|
|
end
|
|
|
|
// The following generate block is implicitly named genblk4 since
|
|
// it belongs to the fourth generate construct in scope "top".
|
|
// The previous generate block would have been
|
|
// named genblk3 if it had not been explicitly named g1
|
|
|
|
for (i = 0; i < 1; i = i + 1)
|
|
// The following generate block is implicitly named genblk1
|
|
// as the first nested generate block in genblk4
|
|
if (1) logic a; // top.genblk4[0].genblk1.a
|
|
|
|
// The following generate block is implicitly named genblk5
|
|
if (1) logic a; // top.genblk5.a
|
|
endmodule
|