Re: [sv-bc] changing the lifetime of begin end block

Note that in most cases, variables outside of tasks and functions don't
need to use automatic storage. There cannot be multiple activations of the
scope except in certain circumstances involving fork..join_any/join_none
inside loops. An implementation might try to optimize the other cases by
treating them as statics regardless of how they were declared. They might
go too far and allow hierarchical references to them as if they were static,
exposing this treatment. That would be a faulty optimization, but would
not necessarily indicate that these variables are not otherwise treated as
automatics.

If you really want to test whether these variables default to automatic,
you should write a testcase that creates multiple simultaneous activations
of the scope, and see whether each gets its own storage.

Steven Sharp
sharp@cadence.com

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