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

Incorrect width on implicit signals #918

Closed
veripoolbot opened this issue May 13, 2015 · 3 comments
Closed

Incorrect width on implicit signals #918

veripoolbot opened this issue May 13, 2015 · 3 comments
Assignees
Labels
area: wrong runtime result Issue involves an incorrect runtine result from Verilated model resolution: fixed Closed; fixed

Comments

@veripoolbot
Copy link
Contributor


Author Name: Patrick Maupin (@pmaupin)
Original Redmine Issue: 918 from https://www.veripool.org
Original Date: 2015-05-13
Original Assignee: Wilson Snyder (@wsnyder)


module dummy1(o);
     output [31:0] o;
     assign o = 32'h12345678;
endmodule

module dummy2(o);
     output [31:0] o;

     dummy1 dummy(x);
     assign o = x;

endmodule

In this code, x is correctly flagged as an implicit wire, but the width of x appears to be propagated up from dummy1, such that the output o of dummy2 is 32h'12345678.

SO, if I just take a pile of code that I'm handed and verilate it as-is, without bothering with the warnings, I get different results than other simulators...

This was tested with 3.872.

Thanks for an awesome piece of software!

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2015-05-14T00:58:18Z


Thanks for the test case; only occurs when there's an ignored WIDTH warning.

Fixed in git towards 3.873.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Patrick Maupin (@pmaupin)
Original Date: 2015-05-14T18:55:04Z


That was quick!

Thanks,
Pat

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2015-06-06T18:05:01Z


In 3.874.

@veripoolbot veripoolbot added area: wrong runtime result Issue involves an incorrect runtine result from Verilated model resolution: fixed Closed; fixed labels Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: wrong runtime result Issue involves an incorrect runtine result from Verilated model resolution: fixed Closed; fixed
Projects
None yet
Development

No branches or pull requests

2 participants