Re: Draft 4 Correction: Syntax 17-13 PLA Modeling System Task

From: Shalom Bresticker (shalom@msil.sps.mot.com)
Date: Wed Feb 09 2000 - 23:56:09 PST

Next message: Clifford E. Cummings: "BTF - VSG Vote on Friday - Stu's register-variable e-mail message"
Previous message: James A. Markevitch: "Re: Verilog 2000 attributes"
Maybe in reply to: Shalom Bresticker: "Draft 4 Correction: Syntax 17-13 PLA Modeling System Task"
Next in thread: Steven Sharp: "Re: Draft 4 Correction: Syntax 17-13 PLA Modeling System Task"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

<x-html>
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Comments inside.
Shalom
 
Steven Sharp wrote:
<blockquote TYPE=CITE>Shalom Bresticker wrote:
> $array_type$logic$format ( memory_identifier [ dimension ] , input_terms
, output_terms ) ;
 >
 > where the brackets around "dimension" are not bold or red, making
the dimension optional.
Actually, this should just be "memory_identifier". The dimension
is NOT
 allowed here. We are specifying the entire memory, not a word
in it. So
 Shalom is partly right, but didn't go far enough.</blockquote>
Well, gosh darn it, why ISN'T the dimension allowed here ?
 Is there another place in the language where that restriction exists
?
 
<blockquote TYPE=CITE>> BTW, I still think the syntax construct names
 >
 > "array_type", "logic",
"format", "input_terms" and
"output_terms"
 >
 > should all be prefixed by "pla_":
 >
 > "pla_array_type", "pla_logic", "pla_format", "pla_input_terms" and
"pla_output_terms"
This is a matter of opinion. Unlike the BNF, these names are local
to this
 syntax block and clearly apply only to PLA tasks.</blockquote>
OK.
 
<blockquote TYPE=CITE>BTW, if we are generalizing the arguments beyond
concatenations of scalars,
 why isn't "input_terms" defined simply as "expression"? All other
similar
 input arguments to system tasks allow expressions.</blockquote>
Agreed.
 That allows mixtures of nets, regs, constants, function calls, etc.
 
<blockquote TYPE=CITE>FWIW, I re-implemented the PLA tasks in NC-Verilog
last week in order to
 speed them up by an order of magnitude. At the same time, I extended
them
 to allow any expression for the input terms and any reg lvalue expression
 for the output terms. So I can say with some assurance that implementing
 this is not a problem :-)</blockquote>
Great. The PLA slowness in NCV was one reason we did not use
NCV on my last project.
 
<blockquote TYPE=CITE>Steven Sharp
 sharp@cadence.com</blockquote>

<pre>--

************************************************************************
Shalom Bresticker email: shalom@msil.sps.mot.com
Motorola Semiconductor Israel, Ltd. Tel #: +972 9 9522268
P.O.B. 2208, Herzlia 46120, ISRAEL Fax #: +972 9 9522444
<A HREF="http://www.motorola-semi.co.il/"><a href="http://www.motorola-semi.co.il/">http://www.motorola-semi.co.il/>>
************************************************************************</pre>
</html>

</x-html>

Next message: Clifford E. Cummings: "BTF - VSG Vote on Friday - Stu's register-variable e-mail message"
Previous message: James A. Markevitch: "Re: Verilog 2000 attributes"
Maybe in reply to: Shalom Bresticker: "Draft 4 Correction: Syntax 17-13 PLA Modeling System Task"
Next in thread: Steven Sharp: "Re: Draft 4 Correction: Syntax 17-13 PLA Modeling System Task"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Mon Jul 08 2002 - 12:54:11 PDT and
sponsored by Boyd Technology, Inc.