luke
/
verilator
mirror of https://github.com/verilator/verilator.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
verilator/test_regress/t/t_json_only_debugcheck.out

3130 lines
207 KiB
Plaintext
Raw Normal View History

Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
{"type":"NETLIST","name":"$root","addr":"(B)","loc":"a,0:0,0:0","timeunit":"1ps","timeprecision":"1ps","typeTablep":"(C)","constPoolp":"(D)","dollarUnitPkgp":"(E)","stdPackagep":"UNLINKED","evalp":"(F)","evalNbap":"(G)","dpiExportTriggerp":"UNLINKED","delaySchedulerp":"UNLINKED","nbaEventp":"UNLINKED","nbaEventTriggerp":"UNLINKED","topScopep":"(H)",
"modulesp": [
Support generic interfaces (#6272)
2025-08-22 12:44:35 +02:00
{"type":"MODULE","name":"$root","addr":"(I)","loc":"d,11:8,11:9","isChecker":false,"isProgram":false,"hasGenericIface":false,"origName":"$root","level":1,"modPublic":true,"inLibrary":false,"dead":false,"recursiveClone":false,"recursive":false,"timeunit":"1ps","inlinesp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Add IMPLICITSTATIC also on procedure variables.
2025-09-22 01:52:19 +02:00
{"type":"VAR","name":"clk","addr":"(J)","loc":"d,15:10,15:13","dtypep":"(K)","origName":"clk","isSc":false,"isPrimaryIO":true,"isPrimaryClock":true,"direction":"INPUT","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":true,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"VSTATICI","varType":"PORT","dtypeName":"logic","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"VAR","name":"t.e","addr":"(L)","loc":"d,24:9,24:10","dtypep":"(M)","origName":"e","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"VSTATICI","varType":"VAR","dtypeName":"my_t","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
Deprecate clocker attribute and --clk option (#6463) The only use for the clocker attribute and the AstVar::isUsedClock that is actually necessary today for correctness is to mark top level inputs of --lib-create blocks as being (or driving) a clock signal. Correctness of --lib-create (and hence hierarchical blocks) actually used to depend on having the right optimizations eliminate intermediate clocks (e.g.: V3Gate), when the top level port was not used directly in a sensitivity list, or marking top level signals manually via --clk or the clocker attribute. However V3Sched::partition already needs to trace through the logic to figure out what signals might drive a sensitivity list, so it can very easily mark all top level inputs as such. In this patch we remove the AstVar::attrClocker and AstVar::isUsedClock attributes, and replace them with AstVar::isPrimaryClock, automatically set by V3Sched::partition. This eliminates all need for manual annotation so we are deprecating the --clk/--no-clk options and the clocker/no_clocker attributes. This also eliminates the opportunity for any further mis-optimization similar to #6453. Regarding the other uses of the removed AstVar attributes: - As of 5.000, initial edges are triggered via a separate mechanism applied in V3Sched, so the use in V3EmitCFunc.cpp is redundant - Also as of 5.000, we can handle arbitrary sensitivity expressions, so the restriction on eliminating clock signals in V3Gate is unnecessary - Since the recent change when Dfg is applied after V3Scope, it does perform the equivalent of GateClkDecomp, so we can delete that pass.
2025-09-20 16:50:22 +02:00
{"type":"VAR","name":"__Vtrigprevexpr___TOP__clk__0","addr":"(N)","loc":"d,11:8,11:9","dtypep":"(K)","origName":"__Vtrigprevexpr___TOP__clk__0","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"NONE","varType":"MODULETEMP","dtypeName":"logic","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"t.cyc","addr":"(O)","loc":"d,23:17,23:20","dtypep":"(P)","origName":"cyc","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"VSTATICI","varType":"VAR","dtypeName":"integer","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"VAR","name":"__VactIterCount","addr":"(Q)","loc":"d,11:8,11:9","dtypep":"(R)","origName":"__VactIterCount","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":true,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"NONE","varType":"MODULETEMP","dtypeName":"bit","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"VAR","name":"__VactTriggered","addr":"(S)","loc":"d,11:8,11:9","dtypep":"(T)","origName":"__VactTriggered","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"NONE","varType":"MODULETEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"VAR","name":"__VnbaTriggered","addr":"(U)","loc":"d,11:8,11:9","dtypep":"(T)","origName":"__VnbaTriggered","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"NONE","varType":"MODULETEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CELL","name":"$unit","addr":"(V)","loc":"a,0:0,0:0","origName":"__024unit","recursive":false,"modp":"(E)","pinsp": [],"paramsp": [],"rangep": [],"intfRefsp": []},
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
{"type":"TOPSCOPE","name":"","addr":"(H)","loc":"d,11:8,11:9","senTreesp": [],
"scopep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SCOPE","name":"TOP","addr":"(W)","loc":"d,11:8,11:9","aboveScopep":"UNLINKED","aboveCellp":"UNLINKED","modp":"(I)","varsp": [],"blocksp": [],"inlinesp": []}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_eval_static","addr":"(X)","loc":"a,0:0,0:0","slow":true,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],"varsp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STMTEXPR","name":"","addr":"(Y)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCALL","name":"","addr":"(Z)","loc":"d,11:8,11:9","dtypep":"(AB)","funcName":"_eval_static__TOP","funcp":"(BB)","argsp": []}
Fix change detection at time 0 (#5864) Initialize "previous value" variables in the static initializer function, instead of the 'initial' blocks function. Fixes #5499
2025-03-18 14:34:04 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(CB)","loc":"d,63:22,63:25","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"clk","addr":"(EB)","loc":"d,63:22,63:25","dtypep":"(DB)","access":"RD","varp":"(J)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vtrigprevexpr___TOP__clk__0","addr":"(FB)","loc":"d,63:22,63:25","dtypep":"(DB)","access":"WR","varp":"(N)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_eval_static__TOP","addr":"(BB)","loc":"d,11:8,11:9","slow":true,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],"varsp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(GB)","loc":"d,23:23,23:24","dtypep":"(P)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'sh0","addr":"(HB)","loc":"d,23:23,23:24","dtypep":"(IB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.cyc","addr":"(JB)","loc":"d,23:23,23:24","dtypep":"(P)","access":"WR","varp":"(O)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_eval_initial","addr":"(KB)","loc":"a,0:0,0:0","slow":true,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],"varsp": [],
Fix change detection at time 0 (#5864) Initialize "previous value" variables in the static initializer function, instead of the 'initial' blocks function. Fixes #5499
2025-03-18 14:34:04 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STMTEXPR","name":"","addr":"(LB)","loc":"d,11:8,11:9",
Fix change detection at time 0 (#5864) Initialize "previous value" variables in the static initializer function, instead of the 'initial' blocks function. Fixes #5499
2025-03-18 14:34:04 +01:00
"exprp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCALL","name":"","addr":"(MB)","loc":"d,11:8,11:9","dtypep":"(AB)","funcName":"_eval_initial__TOP","funcp":"(NB)","argsp": []}
Fix change detection at time 0 (#5864) Initialize "previous value" variables in the static initializer function, instead of the 'initial' blocks function. Fixes #5499
2025-03-18 14:34:04 +01:00
]}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_eval_initial__TOP","addr":"(NB)","loc":"d,11:8,11:9","slow":true,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
"varsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"__Vtemp_1","addr":"(OB)","loc":"d,49:120,49:121","dtypep":"(PB)","origName":"__Vtemp_1","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"NONE","varType":"STMTTEMP","dtypeName":"string","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(QB)","loc":"d,32:9,32:10","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(SB)","loc":"d,32:11,32:14","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(TB)","loc":"d,32:7,32:8","dtypep":"(RB)","access":"WR","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(UB)","loc":"d,38:10,38:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(VB)","loc":"d,38:26,38:29","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(WB)","loc":"d,38:31,38:34","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(XB)","loc":"d,38:15,38:16","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(YB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(BC)","loc":"d,38:15,38:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(DC)","loc":"d,38:15,38:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(FC)","loc":"d,38:15,38:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(GC)","loc":"d,38:15,38:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(HC)","loc":"d,38:43,38:49",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:38: got='h%x exp='h4\\n","addr":"(IC)","loc":"d,38:43,38:49","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(JC)","loc":"d,38:122,38:123","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(KC)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(LC)","loc":"d,38:122,38:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(MC)","loc":"d,38:122,38:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(NC)","loc":"d,38:122,38:123","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(OC)","loc":"d,38:122,38:123","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(PC)","loc":"d,38:142,38:147","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(QC)","loc":"d,39:10,39:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(RC)","loc":"d,39:34,39:37","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(SC)","loc":"d,39:39,39:42","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(TC)","loc":"d,39:15,39:16","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(UC)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(VC)","loc":"d,39:15,39:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(WC)","loc":"d,39:15,39:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(XC)","loc":"d,39:15,39:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(YC)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(ZC)","loc":"d,39:15,39:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(AD)","loc":"d,39:15,39:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(BD)","loc":"d,39:15,39:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(CD)","loc":"d,39:15,39:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(DD)","loc":"d,39:51,39:57",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:39: got='h%x exp='h1\\n","addr":"(ED)","loc":"d,39:51,39:57","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(FD)","loc":"d,39:130,39:131","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(GD)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(HD)","loc":"d,39:130,39:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(ID)","loc":"d,39:130,39:131","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(JD)","loc":"d,39:130,39:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(KD)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(LD)","loc":"d,39:130,39:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(MD)","loc":"d,39:130,39:131","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(ND)","loc":"d,39:130,39:131","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(OD)","loc":"d,39:130,39:131","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(PD)","loc":"d,39:158,39:163","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(QD)","loc":"d,40:10,40:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(RD)","loc":"d,40:26,40:29","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(SD)","loc":"d,40:31,40:34","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(TD)","loc":"d,40:15,40:16","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(UD)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(VD)","loc":"d,40:15,40:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(WD)","loc":"d,40:15,40:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(XD)","loc":"d,40:15,40:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(YD)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(ZD)","loc":"d,40:15,40:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(AE)","loc":"d,40:15,40:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(BE)","loc":"d,40:15,40:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(CE)","loc":"d,40:15,40:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(DE)","loc":"d,40:43,40:49",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:40: got='h%x exp='h1\\n","addr":"(EE)","loc":"d,40:43,40:49","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(FE)","loc":"d,40:122,40:123","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(GE)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(HE)","loc":"d,40:122,40:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(IE)","loc":"d,40:122,40:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(JE)","loc":"d,40:122,40:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(KE)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(LE)","loc":"d,40:122,40:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(ME)","loc":"d,40:122,40:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(NE)","loc":"d,40:122,40:123","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(OE)","loc":"d,40:122,40:123","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(PE)","loc":"d,40:142,40:147","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(QE)","loc":"d,41:10,41:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(RE)","loc":"d,41:42,41:45","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(SE)","loc":"d,41:47,41:50","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(TE)","loc":"d,41:15,41:16","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(UE)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(VE)","loc":"d,41:15,41:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(WE)","loc":"d,41:15,41:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(XE)","loc":"d,41:15,41:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(YE)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(ZE)","loc":"d,41:15,41:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(AF)","loc":"d,41:15,41:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(BF)","loc":"d,41:15,41:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(CF)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(DF)","loc":"d,41:15,41:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(EF)","loc":"d,41:15,41:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(FF)","loc":"d,41:15,41:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(GF)","loc":"d,41:15,41:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(HF)","loc":"d,41:59,41:65",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:41: got='h%x exp='h3\\n","addr":"(IF)","loc":"d,41:59,41:65","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(JF)","loc":"d,41:138,41:139","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(KF)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(LF)","loc":"d,41:138,41:139","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(MF)","loc":"d,41:138,41:139","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(NF)","loc":"d,41:138,41:139","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(OF)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(PF)","loc":"d,41:138,41:139","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(QF)","loc":"d,41:138,41:139","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(RF)","loc":"d,41:138,41:139","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(SF)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(TF)","loc":"d,41:138,41:139","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(UF)","loc":"d,41:138,41:139","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(VF)","loc":"d,41:138,41:139","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(WF)","loc":"d,41:138,41:139","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(XF)","loc":"d,41:174,41:179","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(YF)","loc":"d,42:10,42:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(ZF)","loc":"d,42:34,42:37","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(AG)","loc":"d,42:39,42:42","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(BG)","loc":"d,42:15,42:16","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(CG)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(DG)","loc":"d,42:15,42:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(EG)","loc":"d,42:15,42:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(FG)","loc":"d,42:15,42:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(GG)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(HG)","loc":"d,42:15,42:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(IG)","loc":"d,42:15,42:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(JG)","loc":"d,42:15,42:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(KG)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(LG)","loc":"d,42:15,42:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(MG)","loc":"d,42:15,42:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(NG)","loc":"d,42:15,42:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(OG)","loc":"d,42:15,42:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(PG)","loc":"d,42:51,42:57",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:42: got='h%x exp='h3\\n","addr":"(QG)","loc":"d,42:51,42:57","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(RG)","loc":"d,42:130,42:131","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(SG)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(TG)","loc":"d,42:130,42:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(UG)","loc":"d,42:130,42:131","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(VG)","loc":"d,42:130,42:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(WG)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(XG)","loc":"d,42:130,42:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(YG)","loc":"d,42:130,42:131","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(ZG)","loc":"d,42:130,42:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(AH)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(BH)","loc":"d,42:130,42:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(CH)","loc":"d,42:130,42:131","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(DH)","loc":"d,42:130,42:131","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(EH)","loc":"d,42:130,42:131","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(FH)","loc":"d,42:158,42:163","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(GH)","loc":"d,43:10,43:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(HH)","loc":"d,43:30,43:33","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(IH)","loc":"d,43:35,43:38","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(JH)","loc":"d,43:15,43:16","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(KH)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(LH)","loc":"d,43:15,43:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(MH)","loc":"d,43:15,43:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(NH)","loc":"d,43:15,43:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(OH)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(PH)","loc":"d,43:15,43:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(QH)","loc":"d,43:15,43:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(RH)","loc":"d,43:15,43:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(SH)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(TH)","loc":"d,43:15,43:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(UH)","loc":"d,43:15,43:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(VH)","loc":"d,43:15,43:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(WH)","loc":"d,43:15,43:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(XH)","loc":"d,43:47,43:53",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:43: got='h%x exp='h3\\n","addr":"(YH)","loc":"d,43:47,43:53","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(ZH)","loc":"d,43:126,43:127","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(AI)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(BI)","loc":"d,43:126,43:127","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(CI)","loc":"d,43:126,43:127","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(DI)","loc":"d,43:126,43:127","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(EI)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(FI)","loc":"d,43:126,43:127","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(GI)","loc":"d,43:126,43:127","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(HI)","loc":"d,43:126,43:127","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(II)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(JI)","loc":"d,43:126,43:127","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(KI)","loc":"d,43:126,43:127","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(LI)","loc":"d,43:126,43:127","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(MI)","loc":"d,43:126,43:127","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(NI)","loc":"d,43:150,43:155","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(OI)","loc":"d,44:10,44:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(PI)","loc":"d,44:23,44:26","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(QI)","loc":"d,44:28,44:31","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(RI)","loc":"d,44:15,44:16","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(SI)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(VI)","loc":"d,44:15,44:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(WI)","loc":"d,44:15,44:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(XI)","loc":"d,44:15,44:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(YI)","loc":"d,44:15,44:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(ZI)","loc":"d,44:40,44:46",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:44: got='h%x exp='h1\\n","addr":"(AJ)","loc":"d,44:40,44:46","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(BJ)","loc":"d,44:119,44:120","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(CJ)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(DJ)","loc":"d,44:119,44:120","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(EJ)","loc":"d,44:119,44:120","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(FJ)","loc":"d,44:119,44:120","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(GJ)","loc":"d,44:119,44:120","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(HJ)","loc":"d,44:136,44:141","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(IJ)","loc":"d,45:10,45:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(JJ)","loc":"d,45:26,45:29","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(KJ)","loc":"d,45:31,45:34","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(LJ)","loc":"d,45:15,45:16","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(MJ)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(NJ)","loc":"d,45:15,45:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(OJ)","loc":"d,45:15,45:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(PJ)","loc":"d,45:15,45:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(QJ)","loc":"d,45:15,45:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(RJ)","loc":"d,45:43,45:49",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:45: got='h%x exp='h1\\n","addr":"(SJ)","loc":"d,45:43,45:49","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(TJ)","loc":"d,45:122,45:123","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(UJ)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(VJ)","loc":"d,45:122,45:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(WJ)","loc":"d,45:122,45:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(XJ)","loc":"d,45:122,45:123","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(YJ)","loc":"d,45:122,45:123","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(ZJ)","loc":"d,45:142,45:147","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(AK)","loc":"d,46:10,46:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(BK)","loc":"d,46:34,46:37","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(CK)","loc":"d,46:39,46:42","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(DK)","loc":"d,46:15,46:16","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(EK)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(FK)","loc":"d,46:15,46:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(GK)","loc":"d,46:15,46:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(HK)","loc":"d,46:15,46:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(IK)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(JK)","loc":"d,46:15,46:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(KK)","loc":"d,46:15,46:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(LK)","loc":"d,46:15,46:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(MK)","loc":"d,46:15,46:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(NK)","loc":"d,46:51,46:57",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:46: got='h%x exp='h4\\n","addr":"(OK)","loc":"d,46:51,46:57","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(PK)","loc":"d,46:130,46:131","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(QK)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(RK)","loc":"d,46:130,46:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(SK)","loc":"d,46:130,46:131","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(TK)","loc":"d,46:130,46:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(UK)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(VK)","loc":"d,46:130,46:131","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(WK)","loc":"d,46:130,46:131","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(XK)","loc":"d,46:130,46:131","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(YK)","loc":"d,46:130,46:131","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(ZK)","loc":"d,46:158,46:163","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(AL)","loc":"d,47:10,47:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(BL)","loc":"d,47:26,47:29","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(CL)","loc":"d,47:31,47:34","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(DL)","loc":"d,47:15,47:16","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(EL)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(FL)","loc":"d,47:15,47:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(GL)","loc":"d,47:15,47:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(HL)","loc":"d,47:15,47:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(IL)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(JL)","loc":"d,47:15,47:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(KL)","loc":"d,47:15,47:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(LL)","loc":"d,47:15,47:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(ML)","loc":"d,47:15,47:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(NL)","loc":"d,47:43,47:49",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:47: got='h%x exp='h4\\n","addr":"(OL)","loc":"d,47:43,47:49","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(PL)","loc":"d,47:122,47:123","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(QL)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(RL)","loc":"d,47:122,47:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(SL)","loc":"d,47:122,47:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(TL)","loc":"d,47:122,47:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(UL)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(VL)","loc":"d,47:122,47:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(WL)","loc":"d,47:122,47:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(XL)","loc":"d,47:122,47:123","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(YL)","loc":"d,47:122,47:123","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(ZL)","loc":"d,47:142,47:147","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(AM)","loc":"d,49:10,49:12",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQN","name":"","addr":"(BM)","loc":"d,49:23,49:25","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"\\\"E03\\\"","addr":"(CM)","loc":"d,49:27,49:32","dtypep":"(PB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(DM)","loc":"d,49:15,49:16","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_name1","addr":"(EM)","loc":"d,17:12,17:16","dtypep":"(FM)","access":"RD","varp":"(GM)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(HM)","loc":"d,49:15,49:16","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(IM)","loc":"d,49:15,49:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(JM)","loc":"d,49:15,49:16","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(KM)","loc":"d,49:15,49:16","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(LM)","loc":"d,49:120,49:121","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(MM)","loc":"d,49:120,49:121","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_name1","addr":"(NM)","loc":"d,17:12,17:16","dtypep":"(FM)","access":"RD","varp":"(GM)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(OM)","loc":"d,49:120,49:121","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(PM)","loc":"d,49:120,49:121","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(QM)","loc":"d,49:120,49:121","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(RM)","loc":"d,49:120,49:121","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vtemp_1","addr":"(SM)","loc":"d,49:120,49:121","dtypep":"(PB)","access":"WR","varp":"(OB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(TM)","loc":"d,49:41,49:47",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:49: got='%@' exp='E03'\\n","addr":"(UM)","loc":"d,49:41,49:47","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vtemp_1","addr":"(VM)","loc":"d,49:120,49:121","dtypep":"(PB)","access":"RD","varp":"(OB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(WM)","loc":"d,49:139,49:144","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(XM)","loc":"d,55:9,55:10","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(YM)","loc":"d,55:13,55:17","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(ZM)","loc":"d,55:7,55:8","dtypep":"(RB)","access":"WR","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Improve Loop unrolling (#6480) (#6493) This patch implements #6480. All loop statements are represented using AstLoop and AstLoopTest. This necessitates rework of the loop unroller to handle loops of arbitrary form. To enable this, I have split the old unroller used for 'generate for' statements and moved it into V3Param, and subsequently rewrote V3Unroll to handle the new representation. V3Unroll can now unroll more complex loops, including with loop conditions containing multiple variable references or inlined functions. Handling the more generic code also requires some restrictions. If a loop contains any of the following, it cannot be unrolled: - A timing control that might suspend the loop - A non-inlined call to a non-pure function These constructs can change the values of variables in the loop, so are generally not safe to unroll if they are present. (We could still unroll if all the variables needed for unrolling are automatic, however we don't do that right now.) These restrictions seem ok in the benchmark suite, where the new unroller can generally unroll many more loops than before.
2025-09-29 16:25:25 +02:00
],"timingControlp": []}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_eval_final","addr":"(AN)","loc":"a,0:0,0:0","slow":true,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],"varsp": [],"stmtsp": []},
{"type":"CFUNC","name":"_eval_settle","addr":"(BN)","loc":"a,0:0,0:0","slow":true,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],"varsp": [],"stmtsp": []},
{"type":"CFUNC","name":"_eval_triggers__act","addr":"(CN)","loc":"a,0:0,0:0","slow":false,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],"varsp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(DN)","loc":"d,11:8,11:9","dtypep":"(EN)",
"rhsp": [
{"type":"CCAST","name":"","addr":"(FN)","loc":"d,63:14,63:21","dtypep":"(GN)","size":64,
"lhsp": [
{"type":"CCAST","name":"","addr":"(HN)","loc":"d,63:14,63:21","dtypep":"(DB)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(IN)","loc":"d,63:14,63:21","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(JN)","loc":"d,63:22,63:25","dtypep":"(DB)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"clk","addr":"(KN)","loc":"d,63:22,63:25","dtypep":"(DB)","access":"RD","varp":"(J)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
"rhsp": [
{"type":"NOT","name":"","addr":"(LN)","loc":"d,63:14,63:21","dtypep":"(DB)",
"lhsp": [
{"type":"CCAST","name":"","addr":"(MN)","loc":"d,63:14,63:21","dtypep":"(DB)","size":32,
"lhsp": [
{"type":"VARREF","name":"__Vtrigprevexpr___TOP__clk__0","addr":"(NN)","loc":"d,63:14,63:21","dtypep":"(DB)","access":"RD","varp":"(N)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
],
"lhsp": [
{"type":"ARRAYSEL","name":"","addr":"(ON)","loc":"d,11:8,11:9","dtypep":"(EN)",
"fromp": [
{"type":"VARREF","name":"__VactTriggered","addr":"(PN)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(S)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],
"bitp": [
{"type":"CONST","name":"32'h0","addr":"(QN)","loc":"d,11:8,11:9","dtypep":"(EC)"}
]}
],"timingControlp": []},
{"type":"ASSIGN","name":"","addr":"(RN)","loc":"d,63:22,63:25","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"clk","addr":"(SN)","loc":"d,63:22,63:25","dtypep":"(DB)","access":"RD","varp":"(J)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vtrigprevexpr___TOP__clk__0","addr":"(TN)","loc":"d,63:22,63:25","dtypep":"(DB)","access":"WR","varp":"(N)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CSTMT","name":"","addr":"(UN)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"nodesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"TEXT","name":"","addr":"(VN)","loc":"d,11:8,11:9","text":"#ifdef VL_DEBUG\n"},
{"type":"TEXT","name":"","addr":"(WN)","loc":"d,11:8,11:9","text":"if (VL_UNLIKELY(vlSymsp->_vm_contextp__->debug())) {\n"},
{"type":"STMTEXPR","name":"","addr":"(XN)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCALL","name":"","addr":"(YN)","loc":"d,11:8,11:9","dtypep":"(AB)","funcName":"_dump_triggers__act","funcp":"(ZN)",
"argsp": [
{"type":"VARREF","name":"__VactTriggered","addr":"(AO)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(S)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"},
{"type":"CONST","name":"\\\"act\\\"","addr":"(BO)","loc":"d,11:8,11:9","dtypep":"(PB)"}
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"TEXT","name":"","addr":"(CO)","loc":"d,11:8,11:9","text":"}\n"},
{"type":"TEXT","name":"","addr":"(DO)","loc":"d,11:8,11:9","text":"#endif"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_dump_triggers__act","addr":"(ZN)","loc":"a,0:0,0:0","slow":true,"isStatic":true,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)",
"argsp": [
{"type":"VAR","name":"triggers","addr":"(EO)","loc":"a,0:0,0:0","dtypep":"(T)","origName":"triggers","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"CONSTREF","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(FO)","loc":"a,0:0,0:0","constructing":true,
"varrefp": [
{"type":"VARREF","name":"triggers","addr":"(GO)","loc":"a,0:0,0:0","dtypep":"(T)","access":"WR","varp":"(EO)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]},
{"type":"VAR","name":"tag","addr":"(HO)","loc":"a,0:0,0:0","dtypep":"(PB)","origName":"tag","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"CONSTREF","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"string","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(IO)","loc":"a,0:0,0:0","constructing":true,
"varrefp": [
{"type":"VARREF","name":"tag","addr":"(JO)","loc":"a,0:0,0:0","dtypep":"(PB)","access":"WR","varp":"(HO)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],"varsp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(KO)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(LO)","loc":"d,11:8,11:9","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h1","addr":"(MO)","loc":"d,11:8,11:9","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NOT","name":"","addr":"(NO)","loc":"d,11:8,11:9","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(OO)","loc":"d,11:8,11:9","dtypep":"(DB)","size":32,
"lhsp": [
{"type":"CCALL","name":"","addr":"(PO)","loc":"d,11:8,11:9","dtypep":"(DB)","funcName":"_trigger_anySet__act","funcp":"(QO)",
"argsp": [
{"type":"VARREF","name":"triggers","addr":"(RO)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(EO)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CSTMT","name":"","addr":"(SO)","loc":"d,11:8,11:9",
Internals: Refactor text based Ast constructs (#6280) (#6571) Remove the large variety of ways raw "text" is represented in the Ast. Particularly, the only thing that represents a string to be emitted in the output is AstText. There are 5 AstNodes that can contain AstText, and V3Emit will throw an error if an AstText is encountered anywhere else: - AstCStmt: Internally generated procedural statements involving raw text. - AstCStmtUser: This is the old AstUCStmt, renamed so it sorts next to AstCStmt, as it's largely equivalent. We should never create this internally unless used to represent user input. It is used for $c, statements in the input, and for some 'systemc_* blocks. - AstCExpr: Internally generaged expression involving raw text. - AstCExprUser: This is the old AstUCFunc, renamed so it sorts next to AstCExpr. It is largely equivalent, but also has more optimizations disabled. This should never be created internally, it is only used for $c expressions in the input. - AstTextBlock: Use by V3ProtectLib only, to generate the hierarchical wrappers. Text "tracking" for indentation is always on for AstCStmt, AstCExpr, and AstTextBlock, as these are always generated by us, and should always be well formed. Tracking is always off for AstCStmtUser and AstCExprUser, as these contain arbitrary user input that might not be safe to parse for indentation. Remove subsequently redundant AstNodeSimpleText and AstNodeText types. This patch also fixes incorrect indentation in emitted waveform tracing functions, and makes the output more readable for hier block SV stubs. With that, all raw text nodes are handled as a proper AstNodeStmt or AstNodeExpr as required for #6280.
2025-10-21 13:41:29 +02:00
"nodesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"TEXT","name":"","addr":"(TO)","loc":"d,11:8,11:9","text":"VL_DBG_MSGS(\" No '\" + "},
{"type":"VARREF","name":"tag","addr":"(UO)","loc":"d,11:8,11:9","dtypep":"(PB)","access":"RD","varp":"(HO)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"},
{"type":"TEXT","name":"","addr":"(VO)","loc":"d,11:8,11:9","text":" + \"' region triggers active\\n\");"}
Internals: Emit newlines for AstCStmt automatically. No functional change intended.
2025-09-26 14:25:47 +02:00
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(WO)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(XO)","loc":"d,11:8,11:9","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h1","addr":"(YO)","loc":"d,11:8,11:9","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(ZO)","loc":"d,11:8,11:9","dtypep":"(DB)","size":32,
"lhsp": [
{"type":"ARRAYSEL","name":"","addr":"(AP)","loc":"d,11:8,11:9","dtypep":"(EN)",
"fromp": [
{"type":"VARREF","name":"triggers","addr":"(BP)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(EO)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],
"bitp": [
{"type":"CONST","name":"32'h0","addr":"(CP)","loc":"d,11:8,11:9","dtypep":"(EC)"}
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CSTMT","name":"","addr":"(DP)","loc":"d,11:8,11:9",
Internals: Refactor text based Ast constructs (#6280) (#6571) Remove the large variety of ways raw "text" is represented in the Ast. Particularly, the only thing that represents a string to be emitted in the output is AstText. There are 5 AstNodes that can contain AstText, and V3Emit will throw an error if an AstText is encountered anywhere else: - AstCStmt: Internally generated procedural statements involving raw text. - AstCStmtUser: This is the old AstUCStmt, renamed so it sorts next to AstCStmt, as it's largely equivalent. We should never create this internally unless used to represent user input. It is used for $c, statements in the input, and for some 'systemc_* blocks. - AstCExpr: Internally generaged expression involving raw text. - AstCExprUser: This is the old AstUCFunc, renamed so it sorts next to AstCExpr. It is largely equivalent, but also has more optimizations disabled. This should never be created internally, it is only used for $c expressions in the input. - AstTextBlock: Use by V3ProtectLib only, to generate the hierarchical wrappers. Text "tracking" for indentation is always on for AstCStmt, AstCExpr, and AstTextBlock, as these are always generated by us, and should always be well formed. Tracking is always off for AstCStmtUser and AstCExprUser, as these contain arbitrary user input that might not be safe to parse for indentation. Remove subsequently redundant AstNodeSimpleText and AstNodeText types. This patch also fixes incorrect indentation in emitted waveform tracing functions, and makes the output more readable for hier block SV stubs. With that, all raw text nodes are handled as a proper AstNodeStmt or AstNodeExpr as required for #6280.
2025-10-21 13:41:29 +02:00
"nodesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"TEXT","name":"","addr":"(EP)","loc":"d,11:8,11:9","text":"VL_DBG_MSGS(\" '\" + "},
{"type":"VARREF","name":"tag","addr":"(FP)","loc":"d,11:8,11:9","dtypep":"(PB)","access":"RD","varp":"(HO)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"},
{"type":"TEXT","name":"","addr":"(GP)","loc":"d,11:8,11:9","text":" + \"' region trigger index 0 is active: @(posedge clk)\\n\");"}
Internals: Refactor text based Ast constructs (#6280) (#6571) Remove the large variety of ways raw "text" is represented in the Ast. Particularly, the only thing that represents a string to be emitted in the output is AstText. There are 5 AstNodes that can contain AstText, and V3Emit will throw an error if an AstText is encountered anywhere else: - AstCStmt: Internally generated procedural statements involving raw text. - AstCStmtUser: This is the old AstUCStmt, renamed so it sorts next to AstCStmt, as it's largely equivalent. We should never create this internally unless used to represent user input. It is used for $c, statements in the input, and for some 'systemc_* blocks. - AstCExpr: Internally generaged expression involving raw text. - AstCExprUser: This is the old AstUCFunc, renamed so it sorts next to AstCExpr. It is largely equivalent, but also has more optimizations disabled. This should never be created internally, it is only used for $c expressions in the input. - AstTextBlock: Use by V3ProtectLib only, to generate the hierarchical wrappers. Text "tracking" for indentation is always on for AstCStmt, AstCExpr, and AstTextBlock, as these are always generated by us, and should always be well formed. Tracking is always off for AstCStmtUser and AstCExprUser, as these contain arbitrary user input that might not be safe to parse for indentation. Remove subsequently redundant AstNodeSimpleText and AstNodeText types. This patch also fixes incorrect indentation in emitted waveform tracing functions, and makes the output more readable for hier block SV stubs. With that, all raw text nodes are handled as a proper AstNodeStmt or AstNodeExpr as required for #6280.
2025-10-21 13:41:29 +02:00
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_trigger_anySet__act","addr":"(QO)","loc":"a,0:0,0:0","slow":false,"isStatic":true,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)",
"argsp": [
{"type":"VAR","name":"in","addr":"(HP)","loc":"a,0:0,0:0","dtypep":"(T)","origName":"in","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"CONSTREF","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(IP)","loc":"a,0:0,0:0","constructing":true,
"varrefp": [
{"type":"VARREF","name":"in","addr":"(JP)","loc":"a,0:0,0:0","dtypep":"(T)","access":"WR","varp":"(HP)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
"varsp": [
{"type":"VAR","name":"n","addr":"(KP)","loc":"a,0:0,0:0","dtypep":"(R)","origName":"n","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":true,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"bit","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []}
],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(LP)","loc":"a,0:0,0:0","dtypep":"(R)",
"rhsp": [
{"type":"CONST","name":"32'h0","addr":"(MP)","loc":"a,0:0,0:0","dtypep":"(EC)"}
],
"lhsp": [
{"type":"VARREF","name":"n","addr":"(NP)","loc":"a,0:0,0:0","dtypep":"(R)","access":"WR","varp":"(KP)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],"timingControlp": []},
{"type":"LOOP","name":"","addr":"(OP)","loc":"d,11:8,11:9","unroll":"default",
"stmtsp": [
{"type":"IF","name":"","addr":"(PP)","loc":"d,11:8,11:9",
"condp": [
{"type":"ARRAYSEL","name":"","addr":"(QP)","loc":"d,11:8,11:9","dtypep":"(EN)",
"fromp": [
{"type":"VARREF","name":"in","addr":"(RP)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(HP)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],
"bitp": [
{"type":"VARREF","name":"n","addr":"(SP)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(KP)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
"thensp": [
{"type":"CRETURN","name":"","addr":"(TP)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"1'h1","addr":"(UP)","loc":"d,11:8,11:9","dtypep":"(DB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
],"elsesp": []},
{"type":"ASSIGN","name":"","addr":"(VP)","loc":"a,0:0,0:0","dtypep":"(R)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ADD","name":"","addr":"(WP)","loc":"a,0:0,0:0","dtypep":"(R)",
"lhsp": [
{"type":"CCAST","name":"","addr":"(XP)","loc":"a,0:0,0:0","dtypep":"(EC)","size":32,
"lhsp": [
{"type":"CONST","name":"32'h1","addr":"(YP)","loc":"a,0:0,0:0","dtypep":"(EC)"}
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
"rhsp": [
{"type":"VARREF","name":"n","addr":"(ZP)","loc":"a,0:0,0:0","dtypep":"(R)","access":"RD","varp":"(KP)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
Split V3Order into further part and decouple various components (#4953) Continuing the idea of decoupling the implementations of the various algorithms. The main points: -Move the former "processDomain" stuff, dealing with assigning combinational logic into the relevant sensitivity domains into V3OrderProcessDomains.cpp -Move the parallel code construction in V3OrderParallel.cpp (Could combine this with some parts of V3Partition - those not called from V3Partition::finalize - but that's not for this patch). -Move the serial code construction into V3OrderSerial.cpp -Factored the very small common code between the parallel and serial code construction (processMoveOneLogic) into V3OrderCFuncEmitter.cpp
2024-03-09 13:43:09 +01:00
],
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
"lhsp": [
{"type":"VARREF","name":"n","addr":"(AQ)","loc":"a,0:0,0:0","dtypep":"(R)","access":"WR","varp":"(KP)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],"timingControlp": []},
{"type":"LOOPTEST","name":"","addr":"(BQ)","loc":"d,11:8,11:9",
"condp": [
{"type":"GT","name":"","addr":"(CQ)","loc":"d,11:8,11:9","dtypep":"(DB)",
"lhsp": [
{"type":"CONST","name":"32'h1","addr":"(DQ)","loc":"d,11:8,11:9","dtypep":"(EC)"}
Split V3Order into further part and decouple various components (#4953) Continuing the idea of decoupling the implementations of the various algorithms. The main points: -Move the former "processDomain" stuff, dealing with assigning combinational logic into the relevant sensitivity domains into V3OrderProcessDomains.cpp -Move the parallel code construction in V3OrderParallel.cpp (Could combine this with some parts of V3Partition - those not called from V3Partition::finalize - but that's not for this patch). -Move the serial code construction into V3OrderSerial.cpp -Factored the very small common code between the parallel and serial code construction (processMoveOneLogic) into V3OrderCFuncEmitter.cpp
2024-03-09 13:43:09 +01:00
],
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
"rhsp": [
{"type":"VARREF","name":"n","addr":"(EQ)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(KP)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Split V3Order into further part and decouple various components (#4953) Continuing the idea of decoupling the implementations of the various algorithms. The main points: -Move the former "processDomain" stuff, dealing with assigning combinational logic into the relevant sensitivity domains into V3OrderProcessDomains.cpp -Move the parallel code construction in V3OrderParallel.cpp (Could combine this with some parts of V3Partition - those not called from V3Partition::finalize - but that's not for this patch). -Move the serial code construction into V3OrderSerial.cpp -Factored the very small common code between the parallel and serial code construction (processMoveOneLogic) into V3OrderCFuncEmitter.cpp
2024-03-09 13:43:09 +01:00
]}
]}
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
],"contsp": []},
{"type":"CRETURN","name":"","addr":"(FQ)","loc":"d,11:8,11:9",
"lhsp": [
{"type":"CONST","name":"1'h0","addr":"(GQ)","loc":"d,11:8,11:9","dtypep":"(DB)"}
]}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_nba_sequent__TOP__0","addr":"(HQ)","loc":"d,23:17,23:20","slow":false,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
"varsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"__Vdly__t.cyc","addr":"(IQ)","loc":"d,23:17,23:20","dtypep":"(P)","origName":"__Vdly__t__DOT__cyc","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"integer","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(JQ)","loc":"d,23:17,23:20","constructing":true,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"varrefp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.cyc","addr":"(KQ)","loc":"d,23:17,23:20","dtypep":"(P)","access":"WR","varp":"(IQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"__Vdly__t.e","addr":"(LQ)","loc":"d,24:9,24:10","dtypep":"(M)","origName":"__Vdly__t__DOT__e","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"my_t","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(MQ)","loc":"d,24:9,24:10","constructing":true,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"varrefp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.e","addr":"(NQ)","loc":"d,24:9,24:10","dtypep":"(M)","access":"WR","varp":"(LQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"__Vtemp_1","addr":"(OQ)","loc":"d,70:123,70:124","dtypep":"(PB)","origName":"__Vtemp_1","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"NONE","varType":"STMTTEMP","dtypeName":"string","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"VAR","name":"__Vtemp_2","addr":"(PQ)","loc":"d,80:123,80:124","dtypep":"(PB)","origName":"__Vtemp_2","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"NONE","varType":"STMTTEMP","dtypeName":"string","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"VAR","name":"__Vtemp_3","addr":"(QQ)","loc":"d,90:123,90:124","dtypep":"(PB)","origName":"__Vtemp_3","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"NONE","varType":"STMTTEMP","dtypeName":"string","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(RQ)","loc":"d,23:17,23:20","dtypep":"(P)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.cyc","addr":"(SQ)","loc":"d,23:17,23:20","dtypep":"(P)","access":"RD","varp":"(O)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.cyc","addr":"(TQ)","loc":"d,23:17,23:20","dtypep":"(P)","access":"WR","varp":"(IQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(UQ)","loc":"d,24:9,24:10","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(VQ)","loc":"d,24:9,24:10","dtypep":"(RB)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.e","addr":"(WQ)","loc":"d,24:9,24:10","dtypep":"(RB)","access":"WR","varp":"(LQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGNDLY","name":"","addr":"(XQ)","loc":"d,64:11,64:13","dtypep":"(P)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ADD","name":"","addr":"(YQ)","loc":"d,64:18,64:19","dtypep":"(P)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(ZQ)","loc":"d,64:20,64:21","dtypep":"(EC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'sh1","addr":"(AR)","loc":"d,64:20,64:21","dtypep":"(IB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.cyc","addr":"(BR)","loc":"d,64:14,64:17","dtypep":"(P)","access":"RD","varp":"(O)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.cyc","addr":"(CR)","loc":"d,64:7,64:10","dtypep":"(P)","access":"WR","varp":"(IQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(DR)","loc":"d,65:7,65:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"EQ","name":"","addr":"(ER)","loc":"d,65:14,65:16","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'sh0","addr":"(FR)","loc":"d,65:16,65:17","dtypep":"(IB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.cyc","addr":"(GR)","loc":"d,65:11,65:14","dtypep":"(P)","access":"RD","varp":"(O)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGNDLY","name":"","addr":"(HR)","loc":"d,67:12,67:14","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(IR)","loc":"d,67:15,67:18","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.e","addr":"(JR)","loc":"d,67:10,67:11","dtypep":"(RB)","access":"WR","varp":"(LQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []}
],
"elsesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(KR)","loc":"d,69:12,69:14",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"EQ","name":"","addr":"(LR)","loc":"d,69:19,69:21","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'sh1","addr":"(MR)","loc":"d,69:21,69:22","dtypep":"(IB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.cyc","addr":"(NR)","loc":"d,69:16,69:19","dtypep":"(P)","access":"RD","varp":"(O)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(OR)","loc":"d,70:13,70:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQN","name":"","addr":"(PR)","loc":"d,70:26,70:28","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"\\\"E01\\\"","addr":"(QR)","loc":"d,70:30,70:35","dtypep":"(PB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(RR)","loc":"d,70:18,70:19","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_name1","addr":"(SR)","loc":"d,17:12,17:16","dtypep":"(FM)","access":"RD","varp":"(GM)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(TR)","loc":"d,70:18,70:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(UR)","loc":"d,70:18,70:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(VR)","loc":"d,70:18,70:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(WR)","loc":"d,70:18,70:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(XR)","loc":"d,70:123,70:124","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(YR)","loc":"d,70:123,70:124","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_name1","addr":"(ZR)","loc":"d,17:12,17:16","dtypep":"(FM)","access":"RD","varp":"(GM)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(AS)","loc":"d,70:123,70:124","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(BS)","loc":"d,70:123,70:124","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(CS)","loc":"d,70:123,70:124","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(DS)","loc":"d,70:123,70:124","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vtemp_1","addr":"(ES)","loc":"d,70:123,70:124","dtypep":"(PB)","access":"WR","varp":"(OQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(FS)","loc":"d,70:44,70:50",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:70: got='%@' exp='E01'\\n","addr":"(GS)","loc":"d,70:44,70:50","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vtemp_1","addr":"(HS)","loc":"d,70:123,70:124","dtypep":"(PB)","access":"RD","varp":"(OQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(IS)","loc":"d,70:142,70:147","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(JS)","loc":"d,71:13,71:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(KS)","loc":"d,71:26,71:29","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(LS)","loc":"d,71:31,71:34","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(MS)","loc":"d,71:18,71:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(NS)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(OS)","loc":"d,71:18,71:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(PS)","loc":"d,71:18,71:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(QS)","loc":"d,71:18,71:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(RS)","loc":"d,71:18,71:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(SS)","loc":"d,71:43,71:49",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:71: got='h%x exp='h3\\n","addr":"(TS)","loc":"d,71:43,71:49","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(US)","loc":"d,71:122,71:123","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(VS)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(WS)","loc":"d,71:122,71:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(XS)","loc":"d,71:122,71:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(YS)","loc":"d,71:122,71:123","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(ZS)","loc":"d,71:122,71:123","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(AT)","loc":"d,71:139,71:144","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(BT)","loc":"d,72:13,72:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(CT)","loc":"d,72:29,72:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(DT)","loc":"d,72:34,72:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(ET)","loc":"d,72:18,72:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(FT)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(GT)","loc":"d,72:18,72:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(HT)","loc":"d,72:18,72:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(IT)","loc":"d,72:18,72:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(JT)","loc":"d,72:18,72:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(KT)","loc":"d,72:46,72:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:72: got='h%x exp='h3\\n","addr":"(LT)","loc":"d,72:46,72:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(MT)","loc":"d,72:125,72:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(NT)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(OT)","loc":"d,72:125,72:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(PT)","loc":"d,72:125,72:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(QT)","loc":"d,72:125,72:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(RT)","loc":"d,72:125,72:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(ST)","loc":"d,72:145,72:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(TT)","loc":"d,73:13,73:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(UT)","loc":"d,73:29,73:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(VT)","loc":"d,73:34,73:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(WT)","loc":"d,73:18,73:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(XT)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(YT)","loc":"d,73:18,73:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(ZT)","loc":"d,73:18,73:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(AU)","loc":"d,73:18,73:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(BU)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(CU)","loc":"d,73:18,73:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(DU)","loc":"d,73:18,73:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(EU)","loc":"d,73:18,73:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(FU)","loc":"d,73:18,73:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(GU)","loc":"d,73:46,73:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:73: got='h%x exp='h4\\n","addr":"(HU)","loc":"d,73:46,73:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(IU)","loc":"d,73:125,73:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(JU)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(KU)","loc":"d,73:125,73:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(LU)","loc":"d,73:125,73:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(MU)","loc":"d,73:125,73:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(NU)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(OU)","loc":"d,73:125,73:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(PU)","loc":"d,73:125,73:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(QU)","loc":"d,73:125,73:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(RU)","loc":"d,73:125,73:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(SU)","loc":"d,73:145,73:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(TU)","loc":"d,74:13,74:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(UU)","loc":"d,74:26,74:29","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(VU)","loc":"d,74:31,74:34","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(WU)","loc":"d,74:18,74:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(XU)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(YU)","loc":"d,74:18,74:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(ZU)","loc":"d,74:18,74:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(AV)","loc":"d,74:18,74:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(BV)","loc":"d,74:18,74:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(CV)","loc":"d,74:43,74:49",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:74: got='h%x exp='h4\\n","addr":"(DV)","loc":"d,74:43,74:49","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(EV)","loc":"d,74:122,74:123","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(FV)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(GV)","loc":"d,74:122,74:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(HV)","loc":"d,74:122,74:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(IV)","loc":"d,74:122,74:123","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(JV)","loc":"d,74:122,74:123","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(KV)","loc":"d,74:139,74:144","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(LV)","loc":"d,75:13,75:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(MV)","loc":"d,75:29,75:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(NV)","loc":"d,75:34,75:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(OV)","loc":"d,75:18,75:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(PV)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(QV)","loc":"d,75:18,75:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(RV)","loc":"d,75:18,75:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(SV)","loc":"d,75:18,75:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(TV)","loc":"d,75:18,75:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(UV)","loc":"d,75:46,75:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:75: got='h%x exp='h4\\n","addr":"(VV)","loc":"d,75:46,75:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(WV)","loc":"d,75:125,75:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(XV)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(YV)","loc":"d,75:125,75:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(ZV)","loc":"d,75:125,75:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(AW)","loc":"d,75:125,75:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(BW)","loc":"d,75:125,75:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(CW)","loc":"d,75:145,75:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(DW)","loc":"d,76:13,76:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(EW)","loc":"d,76:29,76:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(FW)","loc":"d,76:34,76:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(GW)","loc":"d,76:18,76:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(HW)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(IW)","loc":"d,76:18,76:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(JW)","loc":"d,76:18,76:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(KW)","loc":"d,76:18,76:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(LW)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(MW)","loc":"d,76:18,76:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(NW)","loc":"d,76:18,76:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(OW)","loc":"d,76:18,76:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(PW)","loc":"d,76:18,76:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(QW)","loc":"d,76:46,76:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:76: got='h%x exp='h3\\n","addr":"(RW)","loc":"d,76:46,76:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(SW)","loc":"d,76:125,76:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(TW)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(UW)","loc":"d,76:125,76:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(VW)","loc":"d,76:125,76:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(WW)","loc":"d,76:125,76:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(XW)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(YW)","loc":"d,76:125,76:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(ZW)","loc":"d,76:125,76:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(AX)","loc":"d,76:125,76:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(BX)","loc":"d,76:125,76:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(CX)","loc":"d,76:145,76:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGNDLY","name":"","addr":"(DX)","loc":"d,77:12,77:14","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(EX)","loc":"d,77:15,77:18","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.e","addr":"(FX)","loc":"d,77:10,77:11","dtypep":"(RB)","access":"WR","varp":"(LQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []}
],
"elsesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(GX)","loc":"d,79:12,79:14",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"EQ","name":"","addr":"(HX)","loc":"d,79:19,79:21","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'sh2","addr":"(IX)","loc":"d,79:21,79:22","dtypep":"(IB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.cyc","addr":"(JX)","loc":"d,79:16,79:19","dtypep":"(P)","access":"RD","varp":"(O)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(KX)","loc":"d,80:13,80:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQN","name":"","addr":"(LX)","loc":"d,80:26,80:28","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"\\\"E03\\\"","addr":"(MX)","loc":"d,80:30,80:35","dtypep":"(PB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(NX)","loc":"d,80:18,80:19","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_name1","addr":"(OX)","loc":"d,17:12,17:16","dtypep":"(FM)","access":"RD","varp":"(GM)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(PX)","loc":"d,80:18,80:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(QX)","loc":"d,80:18,80:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(RX)","loc":"d,80:18,80:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(SX)","loc":"d,80:18,80:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(TX)","loc":"d,80:123,80:124","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(UX)","loc":"d,80:123,80:124","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_name1","addr":"(VX)","loc":"d,17:12,17:16","dtypep":"(FM)","access":"RD","varp":"(GM)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(WX)","loc":"d,80:123,80:124","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(XX)","loc":"d,80:123,80:124","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(YX)","loc":"d,80:123,80:124","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(ZX)","loc":"d,80:123,80:124","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vtemp_2","addr":"(AY)","loc":"d,80:123,80:124","dtypep":"(PB)","access":"WR","varp":"(PQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(BY)","loc":"d,80:44,80:50",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:80: got='%@' exp='E03'\\n","addr":"(CY)","loc":"d,80:44,80:50","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vtemp_2","addr":"(DY)","loc":"d,80:123,80:124","dtypep":"(PB)","access":"RD","varp":"(PQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(EY)","loc":"d,80:142,80:147","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(FY)","loc":"d,81:13,81:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(GY)","loc":"d,81:26,81:29","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(HY)","loc":"d,81:31,81:34","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(IY)","loc":"d,81:18,81:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(JY)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(KY)","loc":"d,81:18,81:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(LY)","loc":"d,81:18,81:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(MY)","loc":"d,81:18,81:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(NY)","loc":"d,81:18,81:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(OY)","loc":"d,81:43,81:49",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:81: got='h%x exp='h4\\n","addr":"(PY)","loc":"d,81:43,81:49","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(QY)","loc":"d,81:122,81:123","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(RY)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(SY)","loc":"d,81:122,81:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(TY)","loc":"d,81:122,81:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(UY)","loc":"d,81:122,81:123","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(VY)","loc":"d,81:122,81:123","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(WY)","loc":"d,81:139,81:144","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(XY)","loc":"d,82:13,82:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(YY)","loc":"d,82:29,82:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(ZY)","loc":"d,82:34,82:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(AZ)","loc":"d,82:18,82:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(BZ)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(CZ)","loc":"d,82:18,82:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(DZ)","loc":"d,82:18,82:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(EZ)","loc":"d,82:18,82:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(FZ)","loc":"d,82:18,82:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(GZ)","loc":"d,82:46,82:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:82: got='h%x exp='h4\\n","addr":"(HZ)","loc":"d,82:46,82:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(IZ)","loc":"d,82:125,82:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(JZ)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(KZ)","loc":"d,82:125,82:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(LZ)","loc":"d,82:125,82:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(MZ)","loc":"d,82:125,82:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(NZ)","loc":"d,82:125,82:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(OZ)","loc":"d,82:145,82:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(PZ)","loc":"d,83:13,83:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(QZ)","loc":"d,83:29,83:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(RZ)","loc":"d,83:34,83:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(SZ)","loc":"d,83:18,83:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(TZ)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(UZ)","loc":"d,83:18,83:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(VZ)","loc":"d,83:18,83:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(WZ)","loc":"d,83:18,83:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(XZ)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(YZ)","loc":"d,83:18,83:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(ZZ)","loc":"d,83:18,83:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(AAB)","loc":"d,83:18,83:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(BAB)","loc":"d,83:18,83:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(CAB)","loc":"d,83:46,83:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:83: got='h%x exp='h1\\n","addr":"(DAB)","loc":"d,83:46,83:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(EAB)","loc":"d,83:125,83:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(FAB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(GAB)","loc":"d,83:125,83:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(HAB)","loc":"d,83:125,83:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(IAB)","loc":"d,83:125,83:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(JAB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(KAB)","loc":"d,83:125,83:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(LAB)","loc":"d,83:125,83:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(MAB)","loc":"d,83:125,83:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(NAB)","loc":"d,83:125,83:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(OAB)","loc":"d,83:145,83:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(PAB)","loc":"d,84:13,84:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(QAB)","loc":"d,84:26,84:29","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(RAB)","loc":"d,84:31,84:34","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(SAB)","loc":"d,84:18,84:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(TAB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(UAB)","loc":"d,84:18,84:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(VAB)","loc":"d,84:18,84:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(WAB)","loc":"d,84:18,84:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(XAB)","loc":"d,84:18,84:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(YAB)","loc":"d,84:43,84:49",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:84: got='h%x exp='h1\\n","addr":"(ZAB)","loc":"d,84:43,84:49","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(ABB)","loc":"d,84:122,84:123","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(BBB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(CBB)","loc":"d,84:122,84:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(DBB)","loc":"d,84:122,84:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(EBB)","loc":"d,84:122,84:123","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(FBB)","loc":"d,84:122,84:123","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(GBB)","loc":"d,84:139,84:144","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(HBB)","loc":"d,85:13,85:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(IBB)","loc":"d,85:29,85:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(JBB)","loc":"d,85:34,85:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(KBB)","loc":"d,85:18,85:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(LBB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(MBB)","loc":"d,85:18,85:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(NBB)","loc":"d,85:18,85:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(OBB)","loc":"d,85:18,85:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(PBB)","loc":"d,85:18,85:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(QBB)","loc":"d,85:46,85:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:85: got='h%x exp='h1\\n","addr":"(RBB)","loc":"d,85:46,85:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(SBB)","loc":"d,85:125,85:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(TBB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(UBB)","loc":"d,85:125,85:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(VBB)","loc":"d,85:125,85:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(WBB)","loc":"d,85:125,85:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(XBB)","loc":"d,85:125,85:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(YBB)","loc":"d,85:145,85:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(ZBB)","loc":"d,86:13,86:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(ACB)","loc":"d,86:29,86:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(BCB)","loc":"d,86:34,86:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(CCB)","loc":"d,86:18,86:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(DCB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(ECB)","loc":"d,86:18,86:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(FCB)","loc":"d,86:18,86:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(GCB)","loc":"d,86:18,86:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(HCB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(ICB)","loc":"d,86:18,86:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(JCB)","loc":"d,86:18,86:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(KCB)","loc":"d,86:18,86:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(LCB)","loc":"d,86:18,86:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(MCB)","loc":"d,86:46,86:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:86: got='h%x exp='h4\\n","addr":"(NCB)","loc":"d,86:46,86:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(OCB)","loc":"d,86:125,86:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(PCB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(QCB)","loc":"d,86:125,86:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(RCB)","loc":"d,86:125,86:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(SCB)","loc":"d,86:125,86:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(TCB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(UCB)","loc":"d,86:125,86:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(VCB)","loc":"d,86:125,86:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(WCB)","loc":"d,86:125,86:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(XCB)","loc":"d,86:125,86:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(YCB)","loc":"d,86:145,86:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGNDLY","name":"","addr":"(ZCB)","loc":"d,87:12,87:14","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(ADB)","loc":"d,87:15,87:18","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.e","addr":"(BDB)","loc":"d,87:10,87:11","dtypep":"(RB)","access":"WR","varp":"(LQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []}
],
"elsesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(CDB)","loc":"d,89:12,89:14",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"EQ","name":"","addr":"(DDB)","loc":"d,89:19,89:21","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'sh3","addr":"(EDB)","loc":"d,89:21,89:22","dtypep":"(IB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.cyc","addr":"(FDB)","loc":"d,89:16,89:19","dtypep":"(P)","access":"RD","varp":"(O)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(GDB)","loc":"d,90:13,90:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQN","name":"","addr":"(HDB)","loc":"d,90:26,90:28","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"\\\"E04\\\"","addr":"(IDB)","loc":"d,90:30,90:35","dtypep":"(PB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(JDB)","loc":"d,90:18,90:19","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_name1","addr":"(KDB)","loc":"d,17:12,17:16","dtypep":"(FM)","access":"RD","varp":"(GM)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(LDB)","loc":"d,90:18,90:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(MDB)","loc":"d,90:18,90:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(NDB)","loc":"d,90:18,90:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(ODB)","loc":"d,90:18,90:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(PDB)","loc":"d,90:123,90:124","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(QDB)","loc":"d,90:123,90:124","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_name1","addr":"(RDB)","loc":"d,17:12,17:16","dtypep":"(FM)","access":"RD","varp":"(GM)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(SDB)","loc":"d,90:123,90:124","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(TDB)","loc":"d,90:123,90:124","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(UDB)","loc":"d,90:123,90:124","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(VDB)","loc":"d,90:123,90:124","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vtemp_3","addr":"(WDB)","loc":"d,90:123,90:124","dtypep":"(PB)","access":"WR","varp":"(QQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(XDB)","loc":"d,90:44,90:50",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:90: got='%@' exp='E04'\\n","addr":"(YDB)","loc":"d,90:44,90:50","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vtemp_3","addr":"(ZDB)","loc":"d,90:123,90:124","dtypep":"(PB)","access":"RD","varp":"(QQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(AEB)","loc":"d,90:142,90:147","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(BEB)","loc":"d,91:13,91:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(CEB)","loc":"d,91:26,91:29","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(DEB)","loc":"d,91:31,91:34","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(EEB)","loc":"d,91:18,91:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(FEB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(GEB)","loc":"d,91:18,91:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(HEB)","loc":"d,91:18,91:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(IEB)","loc":"d,91:18,91:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(JEB)","loc":"d,91:18,91:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(KEB)","loc":"d,91:43,91:49",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:91: got='h%x exp='h1\\n","addr":"(LEB)","loc":"d,91:43,91:49","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(MEB)","loc":"d,91:122,91:123","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(NEB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(OEB)","loc":"d,91:122,91:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(PEB)","loc":"d,91:122,91:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(QEB)","loc":"d,91:122,91:123","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(REB)","loc":"d,91:122,91:123","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(SEB)","loc":"d,91:139,91:144","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(TEB)","loc":"d,92:13,92:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(UEB)","loc":"d,92:29,92:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(VEB)","loc":"d,92:34,92:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(WEB)","loc":"d,92:18,92:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(XEB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(YEB)","loc":"d,92:18,92:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(ZEB)","loc":"d,92:18,92:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(AFB)","loc":"d,92:18,92:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(BFB)","loc":"d,92:18,92:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(CFB)","loc":"d,92:46,92:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:92: got='h%x exp='h1\\n","addr":"(DFB)","loc":"d,92:46,92:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(EFB)","loc":"d,92:125,92:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(FFB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(GFB)","loc":"d,92:125,92:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(HFB)","loc":"d,92:125,92:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(IFB)","loc":"d,92:125,92:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(JFB)","loc":"d,92:125,92:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(KFB)","loc":"d,92:145,92:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(LFB)","loc":"d,93:13,93:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(MFB)","loc":"d,93:29,93:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(NFB)","loc":"d,93:34,93:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(OFB)","loc":"d,93:18,93:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(PFB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(QFB)","loc":"d,93:18,93:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(RFB)","loc":"d,93:18,93:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(SFB)","loc":"d,93:18,93:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(TFB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(UFB)","loc":"d,93:18,93:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(VFB)","loc":"d,93:18,93:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(WFB)","loc":"d,93:18,93:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(XFB)","loc":"d,93:18,93:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(YFB)","loc":"d,93:46,93:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:93: got='h%x exp='h3\\n","addr":"(ZFB)","loc":"d,93:46,93:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(AGB)","loc":"d,93:125,93:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(BGB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(CGB)","loc":"d,93:125,93:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(DGB)","loc":"d,93:125,93:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(EGB)","loc":"d,93:125,93:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(FGB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"RD","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(GGB)","loc":"d,93:125,93:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(HGB)","loc":"d,93:125,93:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(IGB)","loc":"d,93:125,93:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(JGB)","loc":"d,93:125,93:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(KGB)","loc":"d,93:145,93:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(LGB)","loc":"d,94:13,94:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(MGB)","loc":"d,94:26,94:29","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(NGB)","loc":"d,94:31,94:34","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(OGB)","loc":"d,94:18,94:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(PGB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(QGB)","loc":"d,94:18,94:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(RGB)","loc":"d,94:18,94:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(SGB)","loc":"d,94:18,94:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(TGB)","loc":"d,94:18,94:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(UGB)","loc":"d,94:43,94:49",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:94: got='h%x exp='h3\\n","addr":"(VGB)","loc":"d,94:43,94:49","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(WGB)","loc":"d,94:122,94:123","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(XGB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(YGB)","loc":"d,94:122,94:123","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(ZGB)","loc":"d,94:122,94:123","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(AHB)","loc":"d,94:122,94:123","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(BHB)","loc":"d,94:122,94:123","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(CHB)","loc":"d,94:139,94:144","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(DHB)","loc":"d,95:13,95:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(EHB)","loc":"d,95:29,95:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(FHB)","loc":"d,95:34,95:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(GHB)","loc":"d,95:18,95:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(HHB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(IHB)","loc":"d,95:18,95:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(JHB)","loc":"d,95:18,95:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(KHB)","loc":"d,95:18,95:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(LHB)","loc":"d,95:18,95:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(MHB)","loc":"d,95:46,95:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:95: got='h%x exp='h3\\n","addr":"(NHB)","loc":"d,95:46,95:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(OHB)","loc":"d,95:125,95:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(PHB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(QHB)","loc":"d,95:125,95:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(RHB)","loc":"d,95:125,95:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(SHB)","loc":"d,95:125,95:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(THB)","loc":"d,95:125,95:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(UHB)","loc":"d,95:145,95:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(VHB)","loc":"d,96:13,96:15",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"NEQ","name":"","addr":"(WHB)","loc":"d,96:29,96:32","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(XHB)","loc":"d,96:34,96:37","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(YHB)","loc":"d,96:18,96:19","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(ZHB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(AIB)","loc":"d,96:18,96:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(BIB)","loc":"d,96:18,96:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(CIB)","loc":"d,96:18,96:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(DIB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(EIB)","loc":"d,96:18,96:19","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(FIB)","loc":"d,96:18,96:19","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(GIB)","loc":"d,96:18,96:19","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(HIB)","loc":"d,96:18,96:19","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(IIB)","loc":"d,96:46,96:52",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"%%Error: t/t_enum_type_methods.v:96: got='h%x exp='h1\\n","addr":"(JIB)","loc":"d,96:46,96:52","dtypep":"(PB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(KIB)","loc":"d,96:125,96:126","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(LIB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(MIB)","loc":"d,96:125,96:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(NIB)","loc":"d,96:125,96:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ARRAYSEL","name":"","addr":"(OIB)","loc":"d,96:125,96:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(PIB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"RD","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"bitp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(QIB)","loc":"d,96:125,96:126","dtypep":"(CC)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(RIB)","loc":"d,96:125,96:126","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(SIB)","loc":"d,96:125,96:126","dtypep":"(CC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(TIB)","loc":"d,96:125,96:126","dtypep":"(CC)","access":"RD","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
]}
]}
]}
],"scopeNamep": []}
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STOP","name":"","addr":"(UIB)","loc":"d,96:145,96:150","isFatal":false}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGNDLY","name":"","addr":"(VIB)","loc":"d,97:12,97:14","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(WIB)","loc":"d,97:15,97:18","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.e","addr":"(XIB)","loc":"d,97:10,97:11","dtypep":"(RB)","access":"WR","varp":"(LQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []}
],
"elsesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(YIB)","loc":"d,99:12,99:14",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"EQ","name":"","addr":"(ZIB)","loc":"d,99:19,99:21","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'sh63","addr":"(AJB)","loc":"d,99:21,99:23","dtypep":"(IB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.cyc","addr":"(BJB)","loc":"d,99:16,99:19","dtypep":"(P)","access":"RD","varp":"(O)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"DISPLAY","name":"","addr":"(CJB)","loc":"d,100:10,100:16",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fmtp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SFORMATF","name":"*-* All Finished *-*\\n","addr":"(DJB)","loc":"d,100:10,100:16","dtypep":"(PB)","exprsp": [],"scopeNamep": []}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"filep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"FINISH","name":"","addr":"(EJB)","loc":"d,101:10,101:17"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"elsesp": []}
]}
]}
]}
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(FJB)","loc":"d,23:17,23:20","dtypep":"(P)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.cyc","addr":"(GJB)","loc":"d,23:17,23:20","dtypep":"(P)","access":"RD","varp":"(IQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.cyc","addr":"(HJB)","loc":"d,23:17,23:20","dtypep":"(P)","access":"WR","varp":"(O)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(IJB)","loc":"d,24:9,24:10","dtypep":"(RB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Vdly__t.e","addr":"(JJB)","loc":"d,24:9,24:10","dtypep":"(RB)","access":"RD","varp":"(LQ)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(KJB)","loc":"d,24:9,24:10","dtypep":"(RB)","access":"WR","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_eval_nba","addr":"(G)","loc":"a,0:0,0:0","slow":false,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],"varsp": [],
"stmtsp": [
{"type":"IF","name":"","addr":"(LJB)","loc":"d,11:8,11:9",
"condp": [
{"type":"AND","name":"","addr":"(MJB)","loc":"d,11:8,11:9","dtypep":"(GN)",
"lhsp": [
{"type":"CONST","name":"64'h1","addr":"(NJB)","loc":"d,11:8,11:9","dtypep":"(GN)"}
],
"rhsp": [
{"type":"ARRAYSEL","name":"","addr":"(OJB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"fromp": [
{"type":"VARREF","name":"__VnbaTriggered","addr":"(PJB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(U)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],
"bitp": [
{"type":"CONST","name":"32'h0","addr":"(QJB)","loc":"d,11:8,11:9","dtypep":"(EC)"}
]}
]}
],
"thensp": [
{"type":"STMTEXPR","name":"","addr":"(RJB)","loc":"d,23:17,23:20",
"exprp": [
{"type":"CCALL","name":"","addr":"(SJB)","loc":"d,23:17,23:20","dtypep":"(AB)","funcName":"_nba_sequent__TOP__0","funcp":"(HQ)","argsp": []}
]}
],"elsesp": []}
]},
{"type":"CFUNC","name":"_trigger_andNot__act","addr":"(TJB)","loc":"a,0:0,0:0","slow":false,"isStatic":true,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)",
"argsp": [
{"type":"VAR","name":"out","addr":"(UJB)","loc":"a,0:0,0:0","dtypep":"(T)","origName":"out","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"OUTPUT","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(VJB)","loc":"a,0:0,0:0","constructing":true,
"varrefp": [
{"type":"VARREF","name":"out","addr":"(WJB)","loc":"a,0:0,0:0","dtypep":"(T)","access":"WR","varp":"(UJB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]},
{"type":"VAR","name":"inA","addr":"(XJB)","loc":"a,0:0,0:0","dtypep":"(T)","origName":"inA","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"CONSTREF","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(YJB)","loc":"a,0:0,0:0","constructing":true,
"varrefp": [
{"type":"VARREF","name":"inA","addr":"(ZJB)","loc":"a,0:0,0:0","dtypep":"(T)","access":"WR","varp":"(XJB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]},
{"type":"VAR","name":"inB","addr":"(AKB)","loc":"a,0:0,0:0","dtypep":"(T)","origName":"inB","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"CONSTREF","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(BKB)","loc":"a,0:0,0:0","constructing":true,
"varrefp": [
{"type":"VARREF","name":"inB","addr":"(CKB)","loc":"a,0:0,0:0","dtypep":"(T)","access":"WR","varp":"(AKB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
"varsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"n","addr":"(DKB)","loc":"a,0:0,0:0","dtypep":"(R)","origName":"n","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":true,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"bit","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(EKB)","loc":"a,0:0,0:0","dtypep":"(R)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h0","addr":"(FKB)","loc":"a,0:0,0:0","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"n","addr":"(GKB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"WR","varp":"(DKB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"LOOP","name":"","addr":"(HKB)","loc":"d,11:8,11:9","unroll":"default",
"stmtsp": [
{"type":"ASSIGN","name":"","addr":"(IKB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"rhsp": [
{"type":"AND","name":"","addr":"(JKB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"lhsp": [
{"type":"ARRAYSEL","name":"","addr":"(KKB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"fromp": [
{"type":"VARREF","name":"inA","addr":"(LKB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(XJB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],
"bitp": [
{"type":"VARREF","name":"n","addr":"(MKB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(DKB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
"rhsp": [
{"type":"NOT","name":"","addr":"(NKB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"lhsp": [
{"type":"ARRAYSEL","name":"","addr":"(OKB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"fromp": [
{"type":"VARREF","name":"inB","addr":"(PKB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(AKB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],
"bitp": [
{"type":"VARREF","name":"n","addr":"(QKB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(DKB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
]}
]}
],
"lhsp": [
{"type":"ARRAYSEL","name":"","addr":"(RKB)","loc":"d,11:8,11:9","dtypep":"(EN)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"out","addr":"(SKB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(UJB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
"bitp": [
{"type":"VARREF","name":"n","addr":"(TKB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(DKB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
],"timingControlp": []},
{"type":"ASSIGN","name":"","addr":"(UKB)","loc":"a,0:0,0:0","dtypep":"(R)",
"rhsp": [
{"type":"ADD","name":"","addr":"(VKB)","loc":"a,0:0,0:0","dtypep":"(R)",
"lhsp": [
{"type":"CCAST","name":"","addr":"(WKB)","loc":"a,0:0,0:0","dtypep":"(EC)","size":32,
"lhsp": [
{"type":"CONST","name":"32'h1","addr":"(XKB)","loc":"a,0:0,0:0","dtypep":"(EC)"}
]}
],
"rhsp": [
{"type":"VARREF","name":"n","addr":"(YKB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"RD","varp":"(DKB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
"lhsp": [
{"type":"VARREF","name":"n","addr":"(ZKB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"WR","varp":"(DKB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],"timingControlp": []},
{"type":"LOOPTEST","name":"","addr":"(ALB)","loc":"d,11:8,11:9",
"condp": [
{"type":"GT","name":"","addr":"(BLB)","loc":"d,11:8,11:9","dtypep":"(DB)",
"lhsp": [
{"type":"CONST","name":"32'h1","addr":"(CLB)","loc":"d,11:8,11:9","dtypep":"(EC)"}
],
"rhsp": [
{"type":"VARREF","name":"n","addr":"(DLB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(DKB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
]}
],"contsp": []}
]},
{"type":"CFUNC","name":"_trigger_orInto__act","addr":"(ELB)","loc":"a,0:0,0:0","slow":false,"isStatic":true,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)",
"argsp": [
{"type":"VAR","name":"out","addr":"(FLB)","loc":"a,0:0,0:0","dtypep":"(T)","origName":"out","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"INOUT","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(GLB)","loc":"a,0:0,0:0","constructing":true,
"varrefp": [
{"type":"VARREF","name":"out","addr":"(HLB)","loc":"a,0:0,0:0","dtypep":"(T)","access":"WR","varp":"(FLB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]},
{"type":"VAR","name":"in","addr":"(ILB)","loc":"a,0:0,0:0","dtypep":"(T)","origName":"in","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"CONSTREF","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(JLB)","loc":"a,0:0,0:0","constructing":true,
"varrefp": [
{"type":"VARREF","name":"in","addr":"(KLB)","loc":"a,0:0,0:0","dtypep":"(T)","access":"WR","varp":"(ILB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
"varsp": [
{"type":"VAR","name":"n","addr":"(LLB)","loc":"a,0:0,0:0","dtypep":"(R)","origName":"n","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":true,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"bit","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []}
],
"stmtsp": [
{"type":"ASSIGN","name":"","addr":"(MLB)","loc":"a,0:0,0:0","dtypep":"(R)",
"rhsp": [
{"type":"CONST","name":"32'h0","addr":"(NLB)","loc":"a,0:0,0:0","dtypep":"(EC)"}
],
"lhsp": [
{"type":"VARREF","name":"n","addr":"(OLB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"WR","varp":"(LLB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],"timingControlp": []},
{"type":"LOOP","name":"","addr":"(PLB)","loc":"d,11:8,11:9","unroll":"default",
"stmtsp": [
{"type":"ASSIGN","name":"","addr":"(QLB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"rhsp": [
{"type":"OR","name":"","addr":"(RLB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"lhsp": [
{"type":"ARRAYSEL","name":"","addr":"(SLB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"fromp": [
{"type":"VARREF","name":"out","addr":"(TLB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(FLB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],
"bitp": [
{"type":"VARREF","name":"n","addr":"(ULB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(LLB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
"rhsp": [
{"type":"ARRAYSEL","name":"","addr":"(VLB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"fromp": [
{"type":"VARREF","name":"in","addr":"(WLB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(ILB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],
"bitp": [
{"type":"VARREF","name":"n","addr":"(XLB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(LLB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
]}
],
"lhsp": [
{"type":"ARRAYSEL","name":"","addr":"(YLB)","loc":"d,11:8,11:9","dtypep":"(EN)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"fromp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"out","addr":"(ZLB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(FLB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
"bitp": [
{"type":"VARREF","name":"n","addr":"(AMB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(LLB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],"timingControlp": []},
{"type":"ASSIGN","name":"","addr":"(BMB)","loc":"a,0:0,0:0","dtypep":"(R)",
"rhsp": [
{"type":"ADD","name":"","addr":"(CMB)","loc":"a,0:0,0:0","dtypep":"(R)",
"lhsp": [
{"type":"CCAST","name":"","addr":"(DMB)","loc":"a,0:0,0:0","dtypep":"(EC)","size":32,
"lhsp": [
{"type":"CONST","name":"32'h1","addr":"(EMB)","loc":"a,0:0,0:0","dtypep":"(EC)"}
]}
],
"rhsp": [
{"type":"VARREF","name":"n","addr":"(FMB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"RD","varp":"(LLB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
"lhsp": [
{"type":"VARREF","name":"n","addr":"(GMB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"WR","varp":"(LLB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],"timingControlp": []},
{"type":"LOOPTEST","name":"","addr":"(HMB)","loc":"d,11:8,11:9",
"condp": [
{"type":"GT","name":"","addr":"(IMB)","loc":"d,11:8,11:9","dtypep":"(DB)",
"lhsp": [
{"type":"CONST","name":"32'h1","addr":"(JMB)","loc":"d,11:8,11:9","dtypep":"(EC)"}
],
"rhsp": [
{"type":"VARREF","name":"n","addr":"(KMB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(LLB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
],"contsp": []}
]},
{"type":"CFUNC","name":"_eval_phase__act","addr":"(LMB)","loc":"a,0:0,0:0","slow":false,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],
"varsp": [
{"type":"VAR","name":"__VpreTriggered","addr":"(MMB)","loc":"d,11:8,11:9","dtypep":"(T)","origName":"__VpreTriggered","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"MODULETEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(NMB)","loc":"d,11:8,11:9","constructing":true,
"varrefp": [
{"type":"VARREF","name":"__VpreTriggered","addr":"(OMB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(MMB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
"stmtsp": [
{"type":"STMTEXPR","name":"","addr":"(PMB)","loc":"a,0:0,0:0",
"exprp": [
{"type":"CCALL","name":"","addr":"(QMB)","loc":"a,0:0,0:0","dtypep":"(AB)","funcName":"_eval_triggers__act","funcp":"(CN)","argsp": []}
]},
{"type":"STMTEXPR","name":"","addr":"(RMB)","loc":"d,11:8,11:9",
"exprp": [
{"type":"CCALL","name":"","addr":"(SMB)","loc":"d,11:8,11:9","dtypep":"(AB)","funcName":"_trigger_andNot__act","funcp":"(TJB)",
"argsp": [
{"type":"VARREF","name":"__VpreTriggered","addr":"(TMB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(MMB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"},
{"type":"VARREF","name":"__VactTriggered","addr":"(UMB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(S)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"},
{"type":"VARREF","name":"__VnbaTriggered","addr":"(VMB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(U)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
]},
{"type":"STMTEXPR","name":"","addr":"(WMB)","loc":"d,11:8,11:9",
"exprp": [
{"type":"CCALL","name":"","addr":"(XMB)","loc":"d,11:8,11:9","dtypep":"(AB)","funcName":"_trigger_orInto__act","funcp":"(ELB)",
"argsp": [
{"type":"VARREF","name":"__VnbaTriggered","addr":"(YMB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(U)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"},
{"type":"VARREF","name":"__VactTriggered","addr":"(ZMB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(S)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
]},
{"type":"CRETURN","name":"","addr":"(ANB)","loc":"a,0:0,0:0",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"1'h0","addr":"(BNB)","loc":"a,0:0,0:0","dtypep":"(DB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_trigger_clear__act","addr":"(CNB)","loc":"a,0:0,0:0","slow":false,"isStatic":true,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)",
"argsp": [
{"type":"VAR","name":"out","addr":"(DNB)","loc":"a,0:0,0:0","dtypep":"(T)","origName":"out","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"OUTPUT","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []},
{"type":"CRESET","name":"","addr":"(ENB)","loc":"a,0:0,0:0","constructing":true,
"varrefp": [
{"type":"VARREF","name":"out","addr":"(FNB)","loc":"a,0:0,0:0","dtypep":"(T)","access":"WR","varp":"(DNB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
"varsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"n","addr":"(GNB)","loc":"a,0:0,0:0","dtypep":"(R)","origName":"n","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":true,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"BLOCKTEMP","dtypeName":"bit","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(HNB)","loc":"a,0:0,0:0","dtypep":"(R)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h0","addr":"(INB)","loc":"a,0:0,0:0","dtypep":"(EC)"}
],
"lhsp": [
{"type":"VARREF","name":"n","addr":"(JNB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"WR","varp":"(GNB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],"timingControlp": []},
{"type":"LOOP","name":"","addr":"(KNB)","loc":"d,11:8,11:9","unroll":"default",
"stmtsp": [
{"type":"ASSIGN","name":"","addr":"(LNB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"rhsp": [
{"type":"CONST","name":"64'h0","addr":"(MNB)","loc":"d,11:8,11:9","dtypep":"(GN)"}
],
"lhsp": [
{"type":"ARRAYSEL","name":"","addr":"(NNB)","loc":"d,11:8,11:9","dtypep":"(EN)",
"fromp": [
{"type":"VARREF","name":"out","addr":"(ONB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(DNB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],
"bitp": [
{"type":"VARREF","name":"n","addr":"(PNB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(GNB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],"timingControlp": []},
{"type":"ASSIGN","name":"","addr":"(QNB)","loc":"a,0:0,0:0","dtypep":"(R)",
"rhsp": [
{"type":"ADD","name":"","addr":"(RNB)","loc":"a,0:0,0:0","dtypep":"(R)",
"lhsp": [
{"type":"CCAST","name":"","addr":"(SNB)","loc":"a,0:0,0:0","dtypep":"(EC)","size":32,
"lhsp": [
{"type":"CONST","name":"32'h1","addr":"(TNB)","loc":"a,0:0,0:0","dtypep":"(EC)"}
]}
],
"rhsp": [
{"type":"VARREF","name":"n","addr":"(UNB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"RD","varp":"(GNB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
],
"lhsp": [
{"type":"VARREF","name":"n","addr":"(VNB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"WR","varp":"(GNB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
],"timingControlp": []},
{"type":"LOOPTEST","name":"","addr":"(WNB)","loc":"d,11:8,11:9",
"condp": [
{"type":"GT","name":"","addr":"(XNB)","loc":"d,11:8,11:9","dtypep":"(DB)",
"lhsp": [
{"type":"CONST","name":"32'h1","addr":"(YNB)","loc":"d,11:8,11:9","dtypep":"(EC)"}
],
"rhsp": [
{"type":"VARREF","name":"n","addr":"(ZNB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(GNB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
]}
],"contsp": []}
]},
{"type":"CFUNC","name":"_eval_phase__nba","addr":"(AOB)","loc":"a,0:0,0:0","slow":false,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],
"varsp": [
{"type":"VAR","name":"__VnbaExecute","addr":"(BOB)","loc":"d,11:8,11:9","dtypep":"(COB)","origName":"__VnbaExecute","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":true,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"MODULETEMP","dtypeName":"bit","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []}
],
"stmtsp": [
{"type":"ASSIGN","name":"","addr":"(DOB)","loc":"a,0:0,0:0","dtypep":"(DB)",
"rhsp": [
{"type":"CCALL","name":"","addr":"(EOB)","loc":"d,11:8,11:9","dtypep":"(DB)","funcName":"_trigger_anySet__act","funcp":"(QO)",
"argsp": [
{"type":"VARREF","name":"__VnbaTriggered","addr":"(FOB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(U)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VnbaExecute","addr":"(GOB)","loc":"a,0:0,0:0","dtypep":"(DB)","access":"WR","varp":"(BOB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(HOB)","loc":"a,0:0,0:0",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VnbaExecute","addr":"(IOB)","loc":"a,0:0,0:0","dtypep":"(DB)","access":"RD","varp":"(BOB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STMTEXPR","name":"","addr":"(JOB)","loc":"a,0:0,0:0",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCALL","name":"","addr":"(KOB)","loc":"a,0:0,0:0","dtypep":"(AB)","funcName":"_eval_nba","funcp":"(G)","argsp": []}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"STMTEXPR","name":"","addr":"(LOB)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCALL","name":"","addr":"(MOB)","loc":"d,11:8,11:9","dtypep":"(AB)","funcName":"_trigger_clear__act","funcp":"(CNB)",
"argsp": [
{"type":"VARREF","name":"__VnbaTriggered","addr":"(NOB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(U)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CRETURN","name":"","addr":"(OOB)","loc":"a,0:0,0:0",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VnbaExecute","addr":"(POB)","loc":"a,0:0,0:0","dtypep":"(DB)","access":"RD","varp":"(BOB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_eval","addr":"(F)","loc":"a,0:0,0:0","slow":false,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"(W)","argsp": [],
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
"varsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"__VnbaIterCount","addr":"(QOB)","loc":"d,11:8,11:9","dtypep":"(R)","origName":"__VnbaIterCount","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":false,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":true,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":true,"lifetime":"NONE","varType":"MODULETEMP","dtypeName":"bit","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],"valuep": [],"attrsp": []}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(ROB)","loc":"d,11:8,11:9","dtypep":"(R)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h0","addr":"(SOB)","loc":"d,11:8,11:9","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VnbaIterCount","addr":"(TOB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"WR","varp":"(QOB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"LOOP","name":"","addr":"(UOB)","loc":"a,0:0,0:0","unroll":"default",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(VOB)","loc":"a,0:0,0:0",
Improve Loop unrolling (#6480) (#6493) This patch implements #6480. All loop statements are represented using AstLoop and AstLoopTest. This necessitates rework of the loop unroller to handle loops of arbitrary form. To enable this, I have split the old unroller used for 'generate for' statements and moved it into V3Param, and subsequently rewrote V3Unroll to handle the new representation. V3Unroll can now unroll more complex loops, including with loop conditions containing multiple variable references or inlined functions. Handling the more generic code also requires some restrictions. If a loop contains any of the following, it cannot be unrolled: - A timing control that might suspend the loop - A non-inlined call to a non-pure function These constructs can change the values of variables in the loop, so are generally not safe to unroll if they are present. (We could still unroll if all the variables needed for unrolling are automatic, however we don't do that right now.) These restrictions seem ok in the benchmark suite, where the new unroller can generally unroll many more loops than before.
2025-09-29 16:25:25 +02:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"LT","name":"","addr":"(WOB)","loc":"a,0:0,0:0","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h64","addr":"(XOB)","loc":"a,0:0,0:0","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VnbaIterCount","addr":"(YOB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"RD","varp":"(QOB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CSTMT","name":"","addr":"(ZOB)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"nodesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"TEXT","name":"","addr":"(APB)","loc":"d,11:8,11:9","text":"#ifdef VL_DEBUG\n"},
{"type":"STMTEXPR","name":"","addr":"(BPB)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCALL","name":"","addr":"(CPB)","loc":"d,11:8,11:9","dtypep":"(AB)","funcName":"_dump_triggers__act","funcp":"(ZN)",
"argsp": [
{"type":"VARREF","name":"__VnbaTriggered","addr":"(DPB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(U)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"},
{"type":"CONST","name":"\\\"nba\\\"","addr":"(EPB)","loc":"d,11:8,11:9","dtypep":"(PB)"}
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"TEXT","name":"","addr":"(FPB)","loc":"d,11:8,11:9","text":"#endif"}
]},
{"type":"CSTMT","name":"","addr":"(GPB)","loc":"a,0:0,0:0",
"nodesp": [
{"type":"TEXT","name":"","addr":"(HPB)","loc":"a,0:0,0:0","text":"VL_FATAL_MT(\"t/t_enum_type_methods.v\", 11, \"\", \"NBA region did not converge after 100 tries\");"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(IPB)","loc":"d,11:8,11:9","dtypep":"(R)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ADD","name":"","addr":"(JPB)","loc":"d,11:8,11:9","dtypep":"(R)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(KPB)","loc":"d,11:8,11:9","dtypep":"(EC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h1","addr":"(LPB)","loc":"d,11:8,11:9","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VnbaIterCount","addr":"(MPB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(QOB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VnbaIterCount","addr":"(NPB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"WR","varp":"(QOB)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(OPB)","loc":"d,11:8,11:9","dtypep":"(R)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h0","addr":"(PPB)","loc":"d,11:8,11:9","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VactIterCount","addr":"(QPB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"WR","varp":"(Q)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"LOOP","name":"","addr":"(RPB)","loc":"a,0:0,0:0","unroll":"default",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(SPB)","loc":"a,0:0,0:0",
Improve Loop unrolling (#6480) (#6493) This patch implements #6480. All loop statements are represented using AstLoop and AstLoopTest. This necessitates rework of the loop unroller to handle loops of arbitrary form. To enable this, I have split the old unroller used for 'generate for' statements and moved it into V3Param, and subsequently rewrote V3Unroll to handle the new representation. V3Unroll can now unroll more complex loops, including with loop conditions containing multiple variable references or inlined functions. Handling the more generic code also requires some restrictions. If a loop contains any of the following, it cannot be unrolled: - A timing control that might suspend the loop - A non-inlined call to a non-pure function These constructs can change the values of variables in the loop, so are generally not safe to unroll if they are present. (We could still unroll if all the variables needed for unrolling are automatic, however we don't do that right now.) These restrictions seem ok in the benchmark suite, where the new unroller can generally unroll many more loops than before.
2025-09-29 16:25:25 +02:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"LT","name":"","addr":"(TPB)","loc":"a,0:0,0:0","dtypep":"(DB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h64","addr":"(UPB)","loc":"a,0:0,0:0","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VactIterCount","addr":"(VPB)","loc":"a,0:0,0:0","dtypep":"(R)","access":"RD","varp":"(Q)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CSTMT","name":"","addr":"(WPB)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"nodesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"TEXT","name":"","addr":"(XPB)","loc":"d,11:8,11:9","text":"#ifdef VL_DEBUG\n"},
{"type":"STMTEXPR","name":"","addr":"(YPB)","loc":"d,11:8,11:9",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"exprp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCALL","name":"","addr":"(ZPB)","loc":"d,11:8,11:9","dtypep":"(AB)","funcName":"_dump_triggers__act","funcp":"(ZN)",
"argsp": [
{"type":"VARREF","name":"__VactTriggered","addr":"(AQB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"RD","varp":"(S)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"},
{"type":"CONST","name":"\\\"act\\\"","addr":"(BQB)","loc":"d,11:8,11:9","dtypep":"(PB)"}
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"TEXT","name":"","addr":"(CQB)","loc":"d,11:8,11:9","text":"#endif"}
]},
{"type":"CSTMT","name":"","addr":"(DQB)","loc":"a,0:0,0:0",
"nodesp": [
{"type":"TEXT","name":"","addr":"(EQB)","loc":"a,0:0,0:0","text":"VL_FATAL_MT(\"t/t_enum_type_methods.v\", 11, \"\", \"Active region did not converge after 100 tries\");"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],"elsesp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ASSIGN","name":"","addr":"(FQB)","loc":"d,11:8,11:9","dtypep":"(R)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ADD","name":"","addr":"(GQB)","loc":"d,11:8,11:9","dtypep":"(R)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCAST","name":"","addr":"(HQB)","loc":"d,11:8,11:9","dtypep":"(EC)","size":32,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h1","addr":"(IQB)","loc":"d,11:8,11:9","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VactIterCount","addr":"(JQB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"RD","varp":"(Q)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VactIterCount","addr":"(KQB)","loc":"d,11:8,11:9","dtypep":"(R)","access":"WR","varp":"(Q)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],"timingControlp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"LOOPTEST","name":"","addr":"(LQB)","loc":"a,0:0,0:0",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCALL","name":"","addr":"(MQB)","loc":"a,0:0,0:0","dtypep":"(DB)","funcName":"_eval_phase__act","funcp":"(LMB)","argsp": []}
]}
Improve Loop unrolling (#6480) (#6493) This patch implements #6480. All loop statements are represented using AstLoop and AstLoopTest. This necessitates rework of the loop unroller to handle loops of arbitrary form. To enable this, I have split the old unroller used for 'generate for' statements and moved it into V3Param, and subsequently rewrote V3Unroll to handle the new representation. V3Unroll can now unroll more complex loops, including with loop conditions containing multiple variable references or inlined functions. Handling the more generic code also requires some restrictions. If a loop contains any of the following, it cannot be unrolled: - A timing control that might suspend the loop - A non-inlined call to a non-pure function These constructs can change the values of variables in the loop, so are generally not safe to unroll if they are present. (We could still unroll if all the variables needed for unrolling are automatic, however we don't do that right now.) These restrictions seem ok in the benchmark suite, where the new unroller can generally unroll many more loops than before.
2025-09-29 16:25:25 +02:00
],"contsp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"LOOPTEST","name":"","addr":"(NQB)","loc":"a,0:0,0:0",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CCALL","name":"","addr":"(OQB)","loc":"a,0:0,0:0","dtypep":"(DB)","funcName":"_eval_phase__nba","funcp":"(AOB)","argsp": []}
]}
Improve Loop unrolling (#6480) (#6493) This patch implements #6480. All loop statements are represented using AstLoop and AstLoopTest. This necessitates rework of the loop unroller to handle loops of arbitrary form. To enable this, I have split the old unroller used for 'generate for' statements and moved it into V3Param, and subsequently rewrote V3Unroll to handle the new representation. V3Unroll can now unroll more complex loops, including with loop conditions containing multiple variable references or inlined functions. Handling the more generic code also requires some restrictions. If a loop contains any of the following, it cannot be unrolled: - A timing control that might suspend the loop - A non-inlined call to a non-pure function These constructs can change the values of variables in the loop, so are generally not safe to unroll if they are present. (We could still unroll if all the variables needed for unrolling are automatic, however we don't do that right now.) These restrictions seem ok in the benchmark suite, where the new unroller can generally unroll many more loops than before.
2025-09-29 16:25:25 +02:00
],"contsp": []}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_eval_debug_assertions","addr":"(PQB)","loc":"d,11:8,11:9","slow":false,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"UNLINKED","argsp": [],"varsp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"IF","name":"","addr":"(QQB)","loc":"d,15:10,15:13",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"condp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"AND","name":"","addr":"(RQB)","loc":"d,15:10,15:13","dtypep":"(K)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"lhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"clk","addr":"(SQB)","loc":"d,15:10,15:13","dtypep":"(K)","access":"RD","varp":"(J)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rhsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"8'hfe","addr":"(TQB)","loc":"d,15:10,15:13","dtypep":"(UQB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],
"thensp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CSTMT","name":"","addr":"(VQB)","loc":"d,15:10,15:13",
Internals: Refactor text based Ast constructs (#6280) (#6571) Remove the large variety of ways raw "text" is represented in the Ast. Particularly, the only thing that represents a string to be emitted in the output is AstText. There are 5 AstNodes that can contain AstText, and V3Emit will throw an error if an AstText is encountered anywhere else: - AstCStmt: Internally generated procedural statements involving raw text. - AstCStmtUser: This is the old AstUCStmt, renamed so it sorts next to AstCStmt, as it's largely equivalent. We should never create this internally unless used to represent user input. It is used for $c, statements in the input, and for some 'systemc_* blocks. - AstCExpr: Internally generaged expression involving raw text. - AstCExprUser: This is the old AstUCFunc, renamed so it sorts next to AstCExpr. It is largely equivalent, but also has more optimizations disabled. This should never be created internally, it is only used for $c expressions in the input. - AstTextBlock: Use by V3ProtectLib only, to generate the hierarchical wrappers. Text "tracking" for indentation is always on for AstCStmt, AstCExpr, and AstTextBlock, as these are always generated by us, and should always be well formed. Tracking is always off for AstCStmtUser and AstCExprUser, as these contain arbitrary user input that might not be safe to parse for indentation. Remove subsequently redundant AstNodeSimpleText and AstNodeText types. This patch also fixes incorrect indentation in emitted waveform tracing functions, and makes the output more readable for hier block SV stubs. With that, all raw text nodes are handled as a proper AstNodeStmt or AstNodeExpr as required for #6280.
2025-10-21 13:41:29 +02:00
"nodesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"TEXT","name":"","addr":"(WQB)","loc":"d,15:10,15:13","text":"Verilated::overWidthError(\"clk\");"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
],"elsesp": []}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFUNC","name":"_ctor_var_reset","addr":"(XQB)","loc":"d,11:8,11:9","slow":true,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"UNLINKED","argsp": [],"varsp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CRESET","name":"","addr":"(YQB)","loc":"d,15:10,15:13","constructing":true,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"varrefp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"clk","addr":"(ZQB)","loc":"d,15:10,15:13","dtypep":"(K)","access":"WR","varp":"(J)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CRESET","name":"","addr":"(ARB)","loc":"d,23:17,23:20","constructing":true,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"varrefp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.cyc","addr":"(BRB)","loc":"d,23:17,23:20","dtypep":"(P)","access":"WR","varp":"(O)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CRESET","name":"","addr":"(CRB)","loc":"d,24:9,24:10","constructing":true,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"varrefp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"t.e","addr":"(DRB)","loc":"d,24:9,24:10","dtypep":"(M)","access":"WR","varp":"(L)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CRESET","name":"","addr":"(ERB)","loc":"d,11:8,11:9","constructing":true,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"varrefp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__VactTriggered","addr":"(FRB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(S)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]},
{"type":"CRESET","name":"","addr":"(GRB)","loc":"d,11:8,11:9","constructing":true,
"varrefp": [
{"type":"VARREF","name":"__Vtrigprevexpr___TOP__clk__0","addr":"(HRB)","loc":"d,11:8,11:9","dtypep":"(K)","access":"WR","varp":"(N)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
]},
{"type":"CRESET","name":"","addr":"(IRB)","loc":"d,11:8,11:9","constructing":true,
"varrefp": [
{"type":"VARREF","name":"__VnbaTriggered","addr":"(JRB)","loc":"d,11:8,11:9","dtypep":"(T)","access":"WR","varp":"(U)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CUSE","name":"$unit","addr":"(KRB)","loc":"a,0:0,0:0","useType":"INT_FWD"}
Internals: Remove unused AstNodeModule 'activesp' child (#6138)
2025-06-29 15:56:44 +02:00
]},
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
{"type":"PACKAGE","name":"$unit","addr":"(E)","loc":"a,0:0,0:0","origName":"__024unit","level":0,"modPublic":false,"inLibrary":true,"dead":false,"recursiveClone":false,"recursive":false,"timeunit":"NONE","inlinesp": [],
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"__Venumtab_enum_next1","addr":"(AC)","loc":"d,17:12,17:16","dtypep":"(ZB)","origName":"__Venumtab_enum_next1","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":true,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"VSTATIC","varType":"MODULETEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITARRAY","name":"","addr":"(LRB)","loc":"d,17:12,17:16","dtypep":"(ZB)","initList":" [1]=(MRB) [3]=(NRB) [4]=(ORB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"defaultp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h0","addr":"(PRB)","loc":"d,17:12,17:16","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"initsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITITEM","name":"","addr":"(MRB)","loc":"d,17:12,17:16",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(QRB)","loc":"d,19:30,19:31","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITITEM","name":"","addr":"(NRB)","loc":"d,17:12,17:16",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(RRB)","loc":"d,20:30,20:31","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITITEM","name":"","addr":"(ORB)","loc":"d,17:12,17:16",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(SRB)","loc":"d,18:30,18:31","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
],"attrsp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"__Venumtab_enum_prev1","addr":"(UI)","loc":"d,17:12,17:16","dtypep":"(TI)","origName":"__Venumtab_enum_prev1","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":true,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"VSTATIC","varType":"MODULETEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITARRAY","name":"","addr":"(TRB)","loc":"d,17:12,17:16","dtypep":"(TI)","initList":" [1]=(URB) [3]=(VRB) [4]=(WRB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"defaultp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h0","addr":"(XRB)","loc":"d,17:12,17:16","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"initsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITITEM","name":"","addr":"(URB)","loc":"d,17:12,17:16",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(YRB)","loc":"d,20:30,20:31","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITITEM","name":"","addr":"(VRB)","loc":"d,17:12,17:16",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(ZRB)","loc":"d,18:30,18:31","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITITEM","name":"","addr":"(WRB)","loc":"d,17:12,17:16",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(ASB)","loc":"d,19:30,19:31","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
],"attrsp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VAR","name":"__Venumtab_enum_name1","addr":"(GM)","loc":"d,17:12,17:16","dtypep":"(FM)","origName":"__Venumtab_enum_name1","isSc":false,"isPrimaryIO":false,"isPrimaryClock":false,"direction":"NONE","isConst":true,"isPullup":false,"isPulldown":false,"isSigPublic":false,"isLatched":false,"isUsedLoopIdx":false,"noReset":false,"attrIsolateAssign":false,"attrFileDescr":false,"isDpiOpenArray":false,"isFuncReturn":false,"isFuncLocal":false,"lifetime":"VSTATIC","varType":"MODULETEMP","dtypeName":"","isSigUserRdPublic":false,"isSigUserRWPublic":false,"isGParam":false,"isParam":false,"attrScBv":false,"attrSFormat":false,"ignorePostWrite":false,"ignoreSchedWrite":false,"sensIfacep":"UNLINKED","childDTypep": [],"delayp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITARRAY","name":"","addr":"(BSB)","loc":"d,17:12,17:16","dtypep":"(FM)","initList":" [1]=(CSB) [3]=(DSB) [4]=(ESB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"defaultp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"\\\"\\\"","addr":"(FSB)","loc":"d,17:12,17:16","dtypep":"(PB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"initsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITITEM","name":"","addr":"(CSB)","loc":"d,17:12,17:16",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"\\\"E01\\\"","addr":"(GSB)","loc":"d,17:12,17:16","dtypep":"(PB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITITEM","name":"","addr":"(DSB)","loc":"d,17:12,17:16",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"\\\"E03\\\"","addr":"(HSB)","loc":"d,17:12,17:16","dtypep":"(PB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"INITITEM","name":"","addr":"(ESB)","loc":"d,17:12,17:16",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"\\\"E04\\\"","addr":"(ISB)","loc":"d,17:12,17:16","dtypep":"(PB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}
],"attrsp": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SCOPE","name":"$unit","addr":"(JSB)","loc":"a,0:0,0:0","aboveScopep":"(W)","aboveCellp":"(V)","modp":"(E)","varsp": [],"blocksp": [],"inlinesp": []},
{"type":"CFUNC","name":"_ctor_var_reset","addr":"(KSB)","loc":"a,0:0,0:0","slow":true,"isStatic":false,"dpiExportDispatcher":false,"dpiExportImpl":false,"dpiImportPrototype":false,"dpiImportWrapper":false,"dpiContext":false,"isConstructor":false,"isDestructor":false,"isVirtual":false,"isCoroutine":false,"needProcess":false,"scopep":"UNLINKED","argsp": [],"varsp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CRESET","name":"","addr":"(LSB)","loc":"d,17:12,17:16","constructing":true,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"varrefp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_next1","addr":"(MSB)","loc":"d,17:12,17:16","dtypep":"(ZB)","access":"WR","varp":"(AC)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Fix non-constant replication in concats (#5171) Signed-off-by: Arkadiusz Kozdra <akozdra@antmicro.com>
2024-06-10 17:21:43 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CRESET","name":"","addr":"(NSB)","loc":"d,17:12,17:16","constructing":true,
Fix non-constant replication in concats (#5171) Signed-off-by: Arkadiusz Kozdra <akozdra@antmicro.com>
2024-06-10 17:21:43 +02:00
"varrefp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_prev1","addr":"(OSB)","loc":"d,17:12,17:16","dtypep":"(TI)","access":"WR","varp":"(UI)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Internals: Emit newlines for AstCStmt automatically. No functional change intended.
2025-09-26 14:25:47 +02:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CRESET","name":"","addr":"(PSB)","loc":"d,17:12,17:16","constructing":true,
Internals: Emit newlines for AstCStmt automatically. No functional change intended.
2025-09-26 14:25:47 +02:00
"varrefp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"VARREF","name":"__Venumtab_enum_name1","addr":"(QSB)","loc":"d,17:12,17:16","dtypep":"(FM)","access":"WR","varp":"(GM)","varScopep":"UNLINKED","classOrPackagep":"UNLINKED"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
Internals: Refactor AstCFunc internals (#6280) (#6578) - Delete 'finalsp'. It was used in one place, basically unnecessary and safe to remove. - Make 'argsp' a 'List[AstVar]'. This held before. It holds the function argument and return variables. - Replace 'intitsp' with 'varsp' and make it into 'List[AstVar]' to hold the function local variables. This was most of its use before. The few places we inserted statements here now moved into 'stmtsp' by inserting at the front of the list.
2025-10-21 17:37:32 +02:00
]}
Internals: Remove unused AstNodeModule 'activesp' child (#6138)
2025-06-29 15:56:44 +02:00
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"filesp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck__Syms.cpp","addr":"(RSB)","loc":"a,0:0,0:0","source":true,"slow":true,"tblockp": []},
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck__Syms.h","addr":"(SSB)","loc":"a,0:0,0:0","source":false,"slow":true,"tblockp": []},
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck.h","addr":"(TSB)","loc":"a,0:0,0:0","source":false,"slow":false,"tblockp": []},
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck.cpp","addr":"(USB)","loc":"a,0:0,0:0","source":true,"slow":false,"tblockp": []},
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck_$root.h","addr":"(VSB)","loc":"a,0:0,0:0","source":false,"slow":false,"tblockp": []},
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck_$unit.h","addr":"(WSB)","loc":"a,0:0,0:0","source":false,"slow":false,"tblockp": []},
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck_$root__Slow.cpp","addr":"(XSB)","loc":"a,0:0,0:0","source":true,"slow":true,"tblockp": []},
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck_$root__0__Slow.cpp","addr":"(YSB)","loc":"a,0:0,0:0","source":true,"slow":true,"tblockp": []},
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck_$root__0.cpp","addr":"(ZSB)","loc":"a,0:0,0:0","source":true,"slow":false,"tblockp": []},
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck_$unit__Slow.cpp","addr":"(ATB)","loc":"a,0:0,0:0","source":true,"slow":true,"tblockp": []},
{"type":"CFILE","name":"obj_vlt/t_json_only_debugcheck/Vt_json_only_debugcheck_$unit__0__Slow.cpp","addr":"(BTB)","loc":"a,0:0,0:0","source":true,"slow":true,"tblockp": []}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"miscsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"TYPETABLE","name":"","addr":"(C)","loc":"a,0:0,0:0","constraintRefp":"UNLINKED","emptyQueuep":"UNLINKED","queueIndexp":"UNLINKED","streamp":"UNLINKED","voidp":"(AB)",
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"typesp": [
{"type":"BASICDTYPE","name":"logic","addr":"(K)","loc":"d,33:24,33:27","dtypep":"(K)","keyword":"logic","generic":true,"rangep": []},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"BASICDTYPE","name":"logic","addr":"(EC)","loc":"d,53:16,53:17","dtypep":"(EC)","keyword":"logic","range":"31:0","generic":true,"rangep": []},
{"type":"BASICDTYPE","name":"logic","addr":"(CTB)","loc":"d,17:17,17:18","dtypep":"(CTB)","keyword":"logic","range":"3:0","generic":true,"rangep": []},
{"type":"ENUMDTYPE","name":"t.my_t","addr":"(DTB)","loc":"d,17:12,17:16","dtypep":"(DTB)","enum":true,"generic":false,"refDTypep":"(CTB)","childDTypep": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"itemsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ENUMITEM","name":"E01","addr":"(ETB)","loc":"d,18:24,18:27","dtypep":"(RB)","rangep": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h1","addr":"(FTB)","loc":"d,18:30,18:31","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ENUMITEM","name":"E03","addr":"(GTB)","loc":"d,19:24,19:27","dtypep":"(RB)","rangep": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h3","addr":"(HTB)","loc":"d,19:30,19:31","dtypep":"(RB)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"ENUMITEM","name":"E04","addr":"(ITB)","loc":"d,20:24,20:27","dtypep":"(RB)","rangep": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"valuep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"4'h4","addr":"(JTB)","loc":"d,20:30,20:31","dtypep":"(RB)"}
]}
]},
{"type":"BASICDTYPE","name":"integer","addr":"(P)","loc":"d,23:4,23:11","dtypep":"(P)","keyword":"integer","range":"31:0","generic":true,"rangep": []},
{"type":"REFDTYPE","name":"my_t","addr":"(M)","loc":"d,24:4,24:8","dtypep":"(DTB)","generic":false,"typedefp":"UNLINKED","refDTypep":"(DTB)","classOrPackagep":"UNLINKED","typeofp": [],"classOrPackageOpp": [],"paramsp": []},
{"type":"BASICDTYPE","name":"string","addr":"(PB)","loc":"d,28:4,28:10","dtypep":"(PB)","keyword":"string","generic":true,"rangep": []},
{"type":"UNPACKARRAYDTYPE","name":"","addr":"(ZB)","loc":"d,17:12,17:16","dtypep":"(ZB)","isCompound":false,"declRange":"[7:0]","generic":false,"refDTypep":"(DTB)","childDTypep": [],
"rangep": [
{"type":"RANGE","name":"","addr":"(KTB)","loc":"d,17:12,17:16","ascending":false,"fromBracket":false,
"leftp": [
{"type":"CONST","name":"32'h7","addr":"(LTB)","loc":"d,17:12,17:16","dtypep":"(EC)"}
],
"rightp": [
{"type":"CONST","name":"32'h0","addr":"(MTB)","loc":"d,17:12,17:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"UNPACKARRAYDTYPE","name":"","addr":"(TI)","loc":"d,17:12,17:16","dtypep":"(TI)","isCompound":false,"declRange":"[7:0]","generic":false,"refDTypep":"(DTB)","childDTypep": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rangep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"RANGE","name":"","addr":"(NTB)","loc":"d,17:12,17:16","ascending":false,"fromBracket":false,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"leftp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(OTB)","loc":"d,17:12,17:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rightp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h0","addr":"(PTB)","loc":"d,17:12,17:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"UNPACKARRAYDTYPE","name":"","addr":"(FM)","loc":"d,17:12,17:16","dtypep":"(FM)","isCompound":true,"declRange":"[7:0]","generic":false,"refDTypep":"(PB)","childDTypep": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rangep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"RANGE","name":"","addr":"(QTB)","loc":"d,17:12,17:16","ascending":false,"fromBracket":false,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"leftp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h7","addr":"(RTB)","loc":"d,17:12,17:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rightp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h0","addr":"(STB)","loc":"d,17:12,17:16","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"BASICDTYPE","name":"logic","addr":"(IB)","loc":"d,23:23,23:24","dtypep":"(IB)","keyword":"logic","range":"31:0","generic":true,"rangep": []},
{"type":"VOIDDTYPE","name":"","addr":"(AB)","loc":"a,0:0,0:0","dtypep":"(AB)","generic":false},
{"type":"BASICDTYPE","name":"bit","addr":"(EN)","loc":"a,0:0,0:0","dtypep":"(EN)","keyword":"bit","range":"63:0","generic":true,"rangep": []},
{"type":"UNPACKARRAYDTYPE","name":"","addr":"(T)","loc":"d,11:8,11:9","dtypep":"(T)","isCompound":false,"declRange":"[0:0]","generic":false,"refDTypep":"(EN)","childDTypep": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"rangep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"RANGE","name":"","addr":"(TTB)","loc":"d,11:8,11:9","ascending":false,"fromBracket":false,
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"leftp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h0","addr":"(UTB)","loc":"d,11:8,11:9","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
],
"rightp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"CONST","name":"32'h0","addr":"(VTB)","loc":"d,11:8,11:9","dtypep":"(EC)"}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]},
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"BASICDTYPE","name":"bit","addr":"(R)","loc":"a,0:0,0:0","dtypep":"(R)","keyword":"bit","range":"31:0","generic":true,"rangep": []},
{"type":"BASICDTYPE","name":"logic","addr":"(GN)","loc":"d,63:14,63:21","dtypep":"(GN)","keyword":"logic","range":"63:0","generic":true,"rangep": []},
{"type":"BASICDTYPE","name":"bit","addr":"(COB)","loc":"d,11:8,11:9","dtypep":"(COB)","keyword":"bit","generic":true,"rangep": []},
{"type":"BASICDTYPE","name":"logic","addr":"(DB)","loc":"d,63:22,63:25","dtypep":"(DB)","keyword":"logic","range":"31:0","generic":true,"rangep": []},
{"type":"BASICDTYPE","name":"logic","addr":"(RB)","loc":"d,32:11,32:14","dtypep":"(RB)","keyword":"logic","range":"31:0","generic":true,"rangep": []},
{"type":"BASICDTYPE","name":"logic","addr":"(CC)","loc":"d,38:15,38:16","dtypep":"(CC)","keyword":"logic","range":"31:0","generic":true,"rangep": []},
{"type":"BASICDTYPE","name":"logic","addr":"(UQB)","loc":"d,15:10,15:13","dtypep":"(UQB)","keyword":"logic","range":"7:0","generic":true,"rangep": []}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]},
{"type":"CONSTPOOL","name":"","addr":"(D)","loc":"a,0:0,0:0",
"modulep": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"MODULE","name":"@CONST-POOL@","addr":"(WTB)","loc":"a,0:0,0:0","isChecker":false,"isProgram":false,"hasGenericIface":false,"origName":"@CONST-POOL@","level":0,"modPublic":false,"inLibrary":false,"dead":false,"recursiveClone":false,"recursive":false,"timeunit":"NONE","inlinesp": [],
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
"stmtsp": [
Internals: Replace VlTriggerVec with unpacked array (#6616) Removed the VlTriggerVec type, and refactored to use an unpacked array of 64-bit words instead. This means the trigger vector and its operations are now the same as for any other unpacked array. The few special functions required for operating on a trigger vector are now generated in V3SchedTrigger as regular AstCFunc if needed. No functional change intended, performance should be the same.
2025-10-31 19:29:11 +01:00
{"type":"SCOPE","name":"TOP","addr":"(XTB)","loc":"a,0:0,0:0","aboveScopep":"UNLINKED","aboveCellp":"UNLINKED","modp":"(WTB)","varsp": [],"blocksp": [],"inlinesp": []}
Internals: Remove unused AstNodeModule 'activesp' child (#6138)
2025-06-29 15:56:44 +02:00
]}
Add --json-only and related JSON dumping (#4715) (#4831).
2024-02-09 23:50:09 +01:00
]}
]}