RE: [sv-bc] Tf ansi nonansi declaration issue.

Mixing of ansi and non-ansi arguments/ports is illegal by the BNF.
However, another vendor didn't catch one particular case mixing ansi and
non-ansi ports, and "a large customer whose name can't be used in
public" wound up with it in their code and "urged" us to support it. I
later ran into an R&D developer at that vendor and he said "oh, that was
a bug".

 

In my opinion, declaring a range without a data type was OK in V1995,
became slightly cumbersome with the introduction of unsigned types in
V2001, and creates a lot of confusion in SV. I wish we would have left
it out of ANSI ports/arguments. We did take it out of enumerated types.

 

Dave

 

 

________________________________

From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On
Behalf Of Daniel Mlynek
Sent: Friday, July 11, 2008 2:24 AM
To: sv-bc@server.eda-stds.org
Cc: 'Przemek Cichon'
Subject: [sv-bc] Tf ansi nonansi declaration issue.

 

I've prepeared couple of tests showing the issues related to tf
declaration.

 

IMHO the LRM doesn't explicitly said what is allwed and what not- all
possible cases and details are in attachment but the problem may be
illustrated by case like below:

 

 

function void f1(input b);
         reg [3:0] b;  //mixture of ANSI and non ANSI like declaration
of tf - imho this should be dupllicate identifier 

    begin
        $display("%b", b);
    end

endfunction

 

Is this known problem? is there mantis for that? - or maybe I've missed
descripition of such cases in LRM?

 

DANiel


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner <http://www.mailscanner.info/> , and is

believed to be clean. 

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