Skip to content

Fix warning "(vcom-1246) Range 1 to 0 is null" for Modelsim/Questa.#1102

Merged
LarsAsplund merged 1 commit intoVUnit:masterfrom
tasgomes:feature/fix-warnings
Jan 5, 2026
Merged

Fix warning "(vcom-1246) Range 1 to 0 is null" for Modelsim/Questa.#1102
LarsAsplund merged 1 commit intoVUnit:masterfrom
tasgomes:feature/fix-warnings

Conversation

@tasgomes
Copy link
Contributor

@tasgomes tasgomes commented Mar 6, 2025

This is a minor fix to avoid unnecessary warnings with Questa and Modelsim.

@nselvara
Copy link

I also once needed a null vector and I also reported a similar issue: #993
I was just wondering if this trick can be used for almost all null vector cases? Sry, for hijacking this PR. 😬

@tasgomes
Copy link
Contributor Author

I would say that yes it can. At least for me, I was able to solve this kind of warnings for Modelsim and Questa using this approach.

@nselvara
Copy link

Thx for the reply. I think then the feature is almost not needed really. Those warnings are for real very annoying...

@tasgomes
Copy link
Contributor Author

tasgomes commented Apr 22, 2025

I have to disagree on the "almost not needed really", specially if we can fix a warning with very low effort like this one. I would rather have a compilation with zero warnings than having avoidable ones that could "hide" important warnings that shall be addressed.

@nselvara
Copy link

Yeah, I agree with you - removing those useless warnings improves the debugging experience.
Btw, I actually meant the null vector as a useless feature. However, I'm not sure if yours could be used in every (corner) case.

@LarsAsplund
Copy link
Collaborator

@tasgomes Thank you for your contribution!

@LarsAsplund LarsAsplund merged commit 32b86fa into VUnit:master Jan 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants