-
Notifications
You must be signed in to change notification settings - Fork 299
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
[BUG] Verible accepting !<reduction&negation_op> without parentheses
rejects-valid syntaxIf the parser wrongly rejects syntactically valid code (according to SV-2017).If the parser wrongly rejects syntactically valid code (according to SV-2017).Status: Open.#2576 In chipsalliance/verible;Disable space before class name parameters
formatterVerilog code formatter issuesVerilog code formatter issuesStatus: Open.#2571 In chipsalliance/verible;verible-verilog-lint does not report multiple drivers on logic / always_ff variables
style-linterVerilog style-linter issuesVerilog style-linter issuesStatus: Open.#2570 In chipsalliance/verible;[BUG] accepting !<reduction_op> without parentheses should be rejected
rejects-valid syntaxIf the parser wrongly rejects syntactically valid code (according to SV-2017).If the parser wrongly rejects syntactically valid code (according to SV-2017).Status: Open.#2569 In chipsalliance/verible;[BUG] Add error on binary use of unary reduction operator ~| and ~&
rejects-valid syntaxIf the parser wrongly rejects syntactically valid code (according to SV-2017).If the parser wrongly rejects syntactically valid code (according to SV-2017).Status: Open.#2568 In chipsalliance/verible;Formatted output is lexically different from the input
formatterVerilog code formatter issuesVerilog code formatter issuesStatus: Open.#2560 In chipsalliance/verible;Formatter: non-convergence wrapping a multi-line sum of long macros in a localparam
formatterVerilog code formatter issuesVerilog code formatter issuesStatus: Open.#2547 In chipsalliance/verible;Formatter: lexical mismatch (MacroIdentifier vs MacroIdItem) when wrapping puts a macro at end of line
formatterVerilog code formatter issuesVerilog code formatter issuesStatus: Open.#2544 In chipsalliance/verible;Verible-verilog format fails when a wrapped assign has a multiline comment
formatterVerilog code formatter issuesVerilog code formatter issuesStatus: Open.#2542 In chipsalliance/verible;Verible-verilog-format fails with Check failed: leading_tokens.empty() || first_tree_token_it == ftokens.end() || first_tree_token_it->before.break_decision != SpacingOptions::kMustWrap
formatterVerilog code formatter issuesVerilog code formatter issuesStatus: Open.#2539 In chipsalliance/verible;- Status: Open.#2537 In chipsalliance/verible;
No support for SV checker construct.
rejects-valid syntaxIf the parser wrongly rejects syntactically valid code (according to SV-2017).If the parser wrongly rejects syntactically valid code (according to SV-2017).Status: Open.#2536 In chipsalliance/verible;