Re: [Iverilog-devel] Updating tests to use `begin_keywords

[Cary R. <cy...@ya...>]

 I have pushed support for this. The normal tests should still be clean. The forced to SystemVerilog tests still have a few (18) failures, but most are because of differences in the compiler when it is parsing Verilog versus SystemVerilog (e.g. error messages, actual functionality supported, etc.). There are four tests that I need to look at in a bit more detail when I have some time. I will probably add a new regression list that overrides some of the tests based on being parsed as SystemVerilog versus Verilog to cleanup the error message differences. The functionality differences may require a bit more creativity.
Cary

    On Sunday, November 22, 2020, 1:35:17 AM PST, Martin Whitaker <ic...@ma...> wrote:  
 
 I can't think of any reason not to do this.

On 21/11/2020 06:45, Cary R. via Iverilog-devel wrote:
> The test suite is being used as part of a larger SystemVerilog testsuite located here: SymbiFlow/sv-tests
> 
> |
> |
> |
> |  |  |
> 
>  |
> 
>  |
> |
> |  |
> SymbiFlow/sv-tests
> 
> Test suite designed to check compliance with the SystemVerilog standard. - SymbiFlow/sv-tests
>  |
> 
>  |
> 
>  |
> 
> 
> Is there any concerns with adding the appropriate `begin_keyword directive to allow some of the older code to be parsed correctly? The plan would be to only add directives to files that cannot be parsed as SystemVerilog without this. I assume we would continue to use the appropriate generation flag in our testsuite since the SymbiFlow test suite will check Icarus with only the -g2012 flag. Probably need to add the appropriate flags, etc to make this -g2017, but that can wait for now.
> 
> Cary
> 
> 
> 
> _______________________________________________
> Iverilog-devel mailing list
> Ive...@li...
> https://lists.sourceforge.net/lists/listinfo/iverilog-devel
> 



_______________________________________________
Iverilog-devel mailing list
Ive...@li...
https://lists.sourceforge.net/lists/listinfo/iverilog-devel