Skip to content
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.

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

AUTOOUTPUTEVERY and AUTOWIRE creates duplicate definitions for signals #1812

Open
engrvns opened this issue Sep 22, 2022 · 2 comments
Open

Comments

@engrvns
Copy link

engrvns commented Sep 22, 2022

Refer Last comment in - #1811
The issue got closed and the comments could have been missed.

@wsnyder > I suspect you want AUTOOUTPUT instead.
@user>
But AUTOOUTPPUT does not promote a signal that's consumed internally as an output port and hardcoding them defeats the purpose.
AUTOOUTPUTEVERY("regex") seems to be a perfect solution for this except duplicate definitions which seems to be a bug.

@wsnyder wsnyder changed the title AUTOOUTPUTEVERY and AUTOWIRE create duplicate definitions for a signal - Possible bug AUTOOUTPUTEVERY and AUTOWIRE creates duplicate definitions for signals Oct 5, 2022
@wsnyder
Copy link
Member

wsnyder commented Oct 5, 2022

The problem here is AUTOOUTPUTEVERY is expanded after AUTOWIRE (and some others) which it needs to be as it wants to output what gets declared by AUTOWIRE (only if it is used but not if it isn't). But this bug wants the opposite order, that is do AUTOOUTPUTEVERY first, but then later do AUTOWIRE.

Obviously both orders can't be satisfied. So at this time I don't see how to implement this case correctly without some major rework I'm not ready to undertake.

@wsnyder
Copy link
Member

wsnyder commented Oct 5, 2022

Note the preexisting autooutputevery_wire.v test shows this exact case.

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

No branches or pull requests

2 participants