Skip to content

Issues: chipsalliance/verible

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

490 Open 491 Closed
490 Open 491 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Installation not successful on MacOS language-server Language server related issues
#2350 opened Feb 6, 2025 by tang-dynasty
Formatter fails to converge due to attribute for port and comment (with a few spaces) after second port definition formatter Verilog code formatter issues
#2349 opened Feb 6, 2025 by david-sawatzke
let construct formatting formatter Verilog code formatter issues
#2348 opened Jan 31, 2025 by Sladkoeshechka
Interface class formatting formatter Verilog code formatter issues
#2347 opened Jan 31, 2025 by Sladkoeshechka
Error lex/parsing-ing formatted output. formatter Verilog code formatter issues
#2346 opened Jan 31, 2025 by Sladkoeshechka
3
prevent formatter from adding space between 'if' and '(' ? formatter Verilog code formatter issues
#2345 opened Jan 30, 2025 by gobbedy
Switch coverage visualization to coverview
#2342 opened Jan 24, 2025 by hzeller
formatter doesn't allow named arguments to be on separate lines? formatter Verilog code formatter issues
#2339 opened Jan 21, 2025 by gobbedy
4
[note]: Can't move abseil-cpp beyond 20240116.* until bazel 6 is retired
#2336 opened Jan 19, 2025 by hzeller
Incorrect wrap with comma at interface declaration and enum formatter Verilog code formatter issues
#2331 opened Jan 16, 2025 by BrianLChen
A lot of code assumes that string_view::iterator is const char*. Does not work on every compiler
#2323 opened Jan 12, 2025 by hzeller
@hzeller
verible-verilog-lint does not work with +incdir+ rejects-valid syntax If the parser wrongly rejects syntactically valid code (according to SV-2017).
#2322 opened Jan 8, 2025 by sifferman
1
[lexcer/parser] Empty content in SV if {} constraint block not supported rejects-valid syntax If the parser wrongly rejects syntactically valid code (according to SV-2017).
#2320 opened Jan 5, 2025 by kaiyushen
[verible-verilog-format] lexer-parser error on long lines: code after parens / braces is missing in code dumped after the error message rejects-valid syntax If the parser wrongly rejects syntactically valid code (according to SV-2017).
#2319 opened Jan 4, 2025 by ckale-openai
3
Option to place _begin_ keyword on a separate line formatter Verilog code formatter issues
#2318 opened Jan 4, 2025 by BrianLChen
format one feature at a time (feature request?) formatter Verilog code formatter issues
#2315 opened Dec 31, 2024 by gobbedy
2
language server crashes when toggling Primary Side Bar (vscode) language-server Language server related issues
#2313 opened Dec 25, 2024 by gobbedy
20
Allow verible.filelist per GitHub submodule language-server Language server related issues
#2290 opened Nov 11, 2024 by thomas-woehrle
2
Formatter is confused by macros formatter Verilog code formatter issues
#2289 opened Nov 7, 2024 by isaacde
how to change lint rule "legacy-generate-region"? enhancement New feature or request good first issue Good for newcomers style-linter Verilog style-linter issues
#2288 opened Nov 7, 2024 by ddppt-yy
6
Formatter splits label from assertion on new line unnecessarily formatter Verilog code formatter issues
#2284 opened Oct 18, 2024 by hankhsu1996
Confusion on camelCase versus PascalCase enhancement New feature or request style-linter Verilog style-linter issues
#2283 opened Oct 12, 2024 by ukanuk
Improve lint rule help enhancement New feature or request good first issue Good for newcomers style-linter Verilog style-linter issues
#2278 opened Oct 6, 2024 by IEncinas10
@batmnnn
3
how to use AUTO-expansion in vscode ? formatter Verilog code formatter issues
#2258 opened Sep 25, 2024 by cheungxi
Alias -i to --inplace formatter Verilog code formatter issues
#2257 opened Sep 25, 2024 by wsnyder
ProTip! Find all open issues with in progress development work with linked:pr.