Subject: Re: problem with incomplete type references in draft 8
From: Kevin Cameron x3251 (Kevin.Cameron@nsc.com)
Date: Fri May 10 2002 - 16:11:55 PDT
> From owner-vlog-pp@eda.org Wed May 8 18:31:34 2002
>
> Peter,
>
> Regarding the issue of deferred types in SystemVerilog, you pointed out that
> there are already two Verilog-2001 constructs which hurt modular
> compilation, parameters and generate blocks.
>
> Parameters certainly are a problem for modular compilation. That is one
> reason that we are deprecating the use of defparams.....
Defparam isn't that much of a problem over parameters themselves, since it
will get executed after initial elaboration and before anything dependent
on a parameter. Deprecating it doesn't buy you much.
>
> Even if deferred types are not frequently used, a conforming tool must be
> able to handle them in all cases. I don't see a point for having deferred
> types, except for the special case of allowing a pointer to a deferred type.
>
> Paul
[Agreed]
Generally for modular compile you would want to limit the variable objects
to outer array indices, as that will only effect memory allocation size at
elaboration/link time. E.g. in C:
extern struct {int foo[4]} bar[]; // OK
extern struct {int foo[]} bar[]; // Disallowed
I.e. it wouldn't hurt too much if only the outer index was being fiddled with
in a generated block.
Kev.
This archive was generated by hypermail 2b28 : Fri May 10 2002 - 16:14:05 PDT