|
From: Cary R. <cy...@ya...> - 2008-01-22 18:49:35
|
A recent problem report for stable had an ifnone construct that
development does not have the functionality to correctly support, so it
errors out requiring you to use -g no-specify to work around the problem.
To me this seems a bit harsh in that we must give up all delay information
because of this one construct. Would it be better to just ignore with a
warning the construct and let the delay go to zero for these cases? You
could get into some weird timing problems by only having partial delays,
so maybe it would be better to just fix the underlying problem.
Thoughts?
You can find the code in pr1877329, but it is basically.
specify
if (B === 1'b1 && CI === 1'b0) ( A => CO ) = (1,1);
if (B === 1'b0 && CI === 1'b1) ( A => CO ) = (1,1);
ifnone ( A => CO ) = (1,1); // elaborate.cc line 3269
endspecify
Cary
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
|