Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > VHDL > clocking on a variable

Reply
Thread Tools

clocking on a variable

 
 
Ralf Hildebrandt
Guest
Posts: n/a
 
      06-19-2004
Hi all!

I just want to hear some opinions about the following (illegal) construct:


process(sig_A,sig_B)
variable clock : std_ulogic;
begin
clock:=sig_A XOR sig_B;
if rising_edge(clock) then
-- do something
end if;
end process;


As I said this is forbidden, because only clocking on a signal is
allowed. My question is: Why? Is it "weak point" in VHDL? Could this be
allowed in the next VHDL standard?


The reason for this construct is just better readable code. Within an
architecture of 1000+ lines of code, dozens of signal are used.
Sometimes similar signals are needed for several registers. Therefore
signal names grow bigger (to make the code readable) and the number of
signals grows. Especially for register-individual clock-gating (to save
power) it would be useful to eliminate all these signals and convert
them to variables.


Ralf
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
clocking muxing, plz throw some light sudeepts@gmail.com VHDL 1 02-23-2006 06:43 PM
Clocking multiple MFT E1 G703 cards? bob@bfisk.demon.co.uk Cisco 2 12-31-2005 06:18 PM
Re: VWIC-2MFT-T1 card and clocking Henry Yen Cisco 0 04-14-2004 11:01 PM
Cisco MC3810 T1 clocking problem Ed M Cisco 3 11-04-2003 04:46 PM
Boundary scan clocking Yves Tchapda VHDL 0 09-17-2003 04:32 PM



Advertisments