RE: [sv-bc] Mantis 3231 proposal

Jonathan,

If you want the LRM to allow functions with intra-assignments delays in nonblocking assignments, I think you will have to file this as a Mantis item.

Regards,
Shalom

> -----Original Message-----
> From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
> Jonathan Bromley
> Sent: Monday, October 25, 2010 10:12 PM
> To: Alsop, Thomas R
> Cc: sv-bc@eda.org
> Subject: Re: [sv-bc] Mantis 3231 proposal
>
> On 25/10/2010 18:33, Alsop, Thomas R wrote:
> > I uploaded a proposal for this issue as well. Hoping we have a
> minute
> > to review today.
> >
> > http://www.eda-stds.org/mantis/view.php?id=3231
> >
> Tom,
>
> I didn't attend BC today so may be repeating stuff
> that was discussed there, but it's interesting that I
> was shot in the foot only today by a simulator that
> takes too literally the wording in 1800-2009/13.4:
>
> A function shall not contain any time-controlled
> statements. That is, any statements containing #
>
> The tool in question rejected this code, because
> the function contains a # time-delay....
>
> function void assign_later(bit b);
> some_signal <= #5 b;
> endfunction
>
> This is surely absurd, and also conflicts with 13.4.4,
> but the wording of 13.4 is overly restrictive and probably
> should be changed. I would like to be able to report this
> as the preposterous bug it is, without getting LRM hair
> splitting from the tool vendor! The point, surely, is that a
> function must not contain any statement that could block
> the flow of execution. "Time-controlled statement" has
> no meaning defined in the LRM and is quite unhelpful.
> Intra-assignment delays of any kind in a nonblocking
> assignment are surely OK in a function.
>
> Thanks
>
> Jonathan Bromley
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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