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

parameter tracing support causes internal error #722

Closed
veripoolbot opened this issue Mar 12, 2014 · 5 comments
Closed

parameter tracing support causes internal error #722

veripoolbot opened this issue Mar 12, 2014 · 5 comments
Assignees

Comments

@veripoolbot
Copy link

@veripoolbot veripoolbot commented Mar 12, 2014


Author Name: Jie Xu (@jiexu)
Original Redmine Issue: 722 from https://www.veripool.org
Original Date: 2014-03-12
Original Assignee: Wilson Snyder (@wsnyder)


The error is "internal error: .., ../V3Task.cpp:1043: func ref not under scope".

The error is generated at the place where a localparam is defined with value calculated using task.

localparam logic [31:0] mask = 32'hff_ff_00_00;
localparam logic [4:0] a = get_size(mask);

Sorry I am not able to reproduce this error with a simple test case. But the error disappear if I remove the commit "add parameters into trace files, #�"

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Mar 14, 2014


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2014-03-14T11:12:34Z


I haven't found this bug yet, but added --no-trace-params as a flag to the git version.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Jul 20, 2014


Original Redmine Comment
Author Name: Jonathon Donaldson
Original Date: 2014-07-20T07:58:02Z


Wilson: I just ran across this bug as well and figured out a way to make it go away without using --no-trace-params. I can probably provide you with a very trivial example that reproduces the issue. It's not clear from your response if you are not able to track it down because you can't reproduce it or you are able to reproduce it but just can't figure it out yet. If you can't reproduce it let me know and I should be able to send you a simple example. I'm using v3.862.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Jul 20, 2014


Original Redmine Comment
Author Name: Jonathon Donaldson
Original Date: 2014-07-20T09:16:31Z


Here is a very trivial example to reproduce the issue. I hope it's helpful...

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Jul 22, 2014


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2014-07-22T00:44:41Z


The test case was exactly what was needed.

Fixed in git towards 3.863.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Sep 21, 2014


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2014-09-21T13:10:42Z


In 3.864.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.