RE: [sv-ac] Updated #1648: default disable

Yes, but it talks only about the first term. The question is whether we
can impose order / content constraint on subsequent terms, i.e., no
other clock, only set / reset type?

ed 

> -----Original Message-----
> From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com] 
> Sent: Friday, March 09, 2007 7:26 AM
> To: Eduard Cerny; Thomas.Thatcher@Sun.COM
> Cc: sv-ac@eda-stds.org
> Subject: RE: [sv-ac] Updated #1648: default disable
> 
> 17.13.5 already imposes an order.
> 
> Shalom
> 
> > -----Original Message-----
> > From: Eduard Cerny [mailto:Eduard.Cerny@synopsys.com]
> > Sent: Friday, March 09, 2007 2:22 PM
> > To: Bresticker, Shalom; Thomas.Thatcher@Sun.COM; Eduard Cerny
> > Cc: sv-ac@eda-stds.org
> > Subject: RE: [sv-ac] Updated #1648: default disable
> > 
> > I suppose that in 1648 we could impose an order and define when
> > inference can be used, i.e., under which order of evet 
> expressions. If
> > not then this inference should be scrapped. what do you say?
> > ed
> > 
> > 
> > > -----Original Message-----
> > > From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com]
> > > Sent: Friday, March 09, 2007 4:57 AM
> > > To: Thomas.Thatcher@Sun.COM; Eduard Cerny
> > > Cc: sv-ac@eda-stds.org
> > > Subject: RE: [sv-ac] Updated #1648: default disable
> > >
> > > It's not wrong.
> > > Synthesis tools do not require the clock to be the first event in
> > the
> > > list.
> > > In fact, the next line after the one you quoted is:
> > >
> > > "// Any sequence of edge events can be in event list."
> > >
> > > Shalom
> > >
> > >
> > > > One other interesting note:  I went to double check the
> > > multiple reset
> > > > conditions by calling up the 1364.1-2002 standard (Verilog RTL
> > > > Synthesis).
> > > > Here's what I read:  (Sec 5.2.2.1, p 9)
> > > >
> > > >     The always statement shall be of the form:
> > > >
> > > > 	always @ (posedge <condA> or negedge <condB> or 
> negedge <condC>
> > > or
> > > > ...
> > > > 		posedge <Clock>)
> > > > 			^^^^^^^??????
> > > > Isn't that backwards?  The clock event should be the first event
> > in
> > > > the list.
> > > > In fact all four examples on the next page have the clock
> > > as the first
> > > > event in the list.
> > >
> 

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.