Honored ContributorI will use don’t care statements in my vhdl code. Quartus 2 have more degree of freedom to reduce logic.
Example: Case aaa IS When 1 => bbb <= 1; When 2 => bbb <= 2; When others => bbb <= (others => ‘-‘); -- don't care END Case; My Question is: What do Quartus with don’t care statements? Will it gnd, vcc or optimise for all options?
Honored Contributortry it and see. Likelyhood is that it will stick them all to '0' or '1'.
Also be carefully with dont cares. elsewhere in the code, if you evaluate b, if you did something like this: if b(0) = '1' then.... Then if b(0) is set to '-' then the evaluation of the expresion is false.Honored ContributorI'm not aware of a std_logic value of '-', where did you get it?
Honored Contributorfrom the std_logic_1164 package:
-------------------------------------------------------------------
-- logic state system (unresolved)
-------------------------------------------------------------------
TYPE std_ulogic IS ( 'U', -- Uninitialized
'X', -- Forcing Unknown
'0', -- Forcing 0
'1', -- Forcing 1
'Z', -- High Impedance
'W', -- Weak Unknown
'L', -- Weak 0
'H', -- Weak 1
'-' -- Don't care
);
SUBTYPE std_logic IS resolved std_ulogic;
Thanks for your answer,
I know that I must be carefully with don’t cares. But if Quartus detect the higher degree of freedom so the can it better optimize. Detect Quartus the higher degree of freedom and can it with the help of this better optimize?Honored ContributorOverall, I think its probably safer just not to use dont cares. I dont think its really going to help the synthesiser optimise things in any meaningful way. But by all means give it a go and see if it makes any difference.
Honored ContributorI'm not sure that this is synthesizable. it might be intended just for simulation.
another question, if you don't cart about the output, why do you specifically define it? (even as don't care) just don't use the others statement.Honored ContributorQuartus will pick up Dont cares, but probably just ignore them, the same way it ignores 'X' statements.
For simulation purposes, it can be useful to specifially produce 'X's, like this example:
if en = '1' then
q <= d;
elsif en = '0' then
null; --hold q
else --catch all for unitialised input enable
q <= 'X';
end if;
I mostly use Verilog, and I'm not familiar so much with VHDL. But if I understand the VHDL code correctly, then it certainly would help Quartus to reduce the logic.
Disregarding the HDL language, any selection logic can be optimized if you are certain that specific values would never happen at the selection input (or if you don't care about the output in that case). --- Quote Start ---
if en = '1' then
q <= d;
elsif en = '0' then
null; --hold q
else --catch all for unitialised input enable
q <= 'X';
end if;
