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

Regression test t_vpi_var fails #615

Closed
veripoolbot opened this issue Feb 8, 2013 · 5 comments
Closed

Regression test t_vpi_var fails #615

veripoolbot opened this issue Feb 8, 2013 · 5 comments
Labels
area: tests Issue involves the testing system resolution: fixed Closed; fixed

Comments

@veripoolbot
Copy link
Contributor


Author Name: Jeremy Bennett (@jeremybennett)
Original Redmine Issue: 615 from https://www.veripool.org
Original Date: 2013-02-08


@t_vpi_var@ gets a mismatch (@rfr[39:0]=0x60064B1CDB@ versus @sig[39:0]=0x00064B1CDB@ in @arr[40]@). I don't know enough about VPI to see where that is going wrong.

%Error: t/t_vpi_var.v:109: Verilog $stop
%Warning: vlt/t_vpi_var: Exec of obj_dir/t_vpi_var/Vt_vpi_var failed

This was on git master branch, commit bcadb0b.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2013-02-08T23:09:58Z


I don't see this. Perhaps there is something initialized in the test that makes it a system specific failure? I had one other similar issue which I had fixed just prior to release, there was an uninitialized variable.

Perhaps post the --verbose output and maybe Rich Porter can help as he was recently there for #�.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Rich Porter
Original Date: 2013-02-09T19:41:01Z


Is it a 32 bit build?

I've reproduced an issue with a 32 bit build - not exactly the same as above but similar.

Wilson did you try 64 or 32 bit build?

I'll fix up the issue I see.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Rich Porter
Original Date: 2013-02-10T10:12:15Z


Some long long confusion using sprintf/sscanf for the decimal string values.

I've tested this patch on 32 & 64 bit builds.

This code should be using the types as defined in verilatedos.h, i.e. vluint64_t.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2013-02-11T12:20:48Z


Thanks for patching!

Patch pushed to git towards 3.846.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2013-03-09T21:51:20Z


In 3.846.

@veripoolbot veripoolbot added area: tests Issue involves the testing system 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: tests Issue involves the testing system resolution: fixed Closed; fixed
Projects
None yet
Development

No branches or pull requests

1 participant