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

BlackBoxFloat #88

Open
shunshou opened this issue Mar 22, 2017 · 2 comments
Open

BlackBoxFloat #88

shunshou opened this issue Mar 22, 2017 · 2 comments

Comments

@shunshou
Copy link
Member

@chick I get these warnings:

%Warning-COMBDLY: /Users/angie.wang/Chisel3FFAST/FFTGen/test_run_dir/FFASTTopTB/dspblocks.fft.FFASTTopSpec260459830/BlackBoxFloat.v:46: Delayed assignments (<=) in non-clocked (non flop or latch) block; suggest blocking assignments (=).
%Warning-COMBDLY: Use "/* verilator lint_off COMBDLY */" and lint_on around source to disable this message.
%Warning-COMBDLY: *** See the manual before disabling this,
%Warning-COMBDLY: else you may end up with different sim results.
%Warning-COMBDLY: /Users/angie.wang/Chisel3FFAST/FFTGen/test_run_dir/FFASTTopTB/dspblocks.fft.FFASTTopSpec260459830/BlackBoxFloat.v:26: Delayed assignments (<=) in non-clocked (non flop or latch) block; suggest blocking assignments (=).
%Warning-COMBDLY: /Users/angie.wang/Chisel3FFAST/FFTGen/test_run_dir/FFASTTopTB/dspblocks.fft.FFASTTopSpec260459830/BlackBoxFloat.v:172: Delayed assignments (<=) in non-clocked (non flop or latch) block; suggest blocking assignments (=).
%Warning-COMBDLY: /Users/angie.wang/Chisel3FFAST/FFTGen/test_run_dir/FFASTTopTB/dspblocks.fft.FFASTTopSpec260459830/BlackBoxFloat.v:16: Delayed assignments (<=) in non-clocked (non flop or latch) block; suggest blocking assignments (=).

Probably best to clean up?

@chick
Copy link
Contributor

chick commented Mar 22, 2017

@shunshou Shouldn't we be able to see these warning running tests in dsptools. I tried changing all <= to =. I didn't see error messages either way and tests passed just the same. I tried running fft, but the git submodule update needed a password
[email protected]'s password:
that I don't think I have

@shunshou
Copy link
Member Author

A couple of things: Seems like Verilator has a major bug, so I'm trying to switch over to VCS. VCS doesn't like the real blackbox stuff unless you add the -sverilog flag. I'll be making a PR at chisel-testers. I'm going to push the <= to = change to ring-refactor. Also, VCS didn't like out w/o reg for some ops. Still debugging and just feeling very sad and overwhelmed.

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