Project

General

Profile

Actions

Bug #10202

closed

SVA grammar warnings via assembling

Added by Sergey Smolov almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
04/03/2020
Due date:
% Done:

0%

Estimated time:
Detected in build:
git
Platform:
Published in build:
0.1.3-beta-201002

Description

> Task :generateGrammarSource
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:342:58:
Decision can match input such as "COMMA DUMMY_attributes DUMMY_port_identifier" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_ALWAYS DUMMY_expression" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control DUMMY_event_control DELAY" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control {KW_NEXTTIME, KW_S_NEXTTIME} LPAREN" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_NOT LPAREN" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control LPAREN LPAREN" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control DUMMY_event_control KW_EVENTUALLY" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_ALWAYS KW_EVENTUALLY" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_S_EVENTUALLY KW_EVENTUALLY" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control {KW_NEXTTIME, KW_S_NEXTTIME} DUMMY_hierarchical_identifier" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_NOT DUMMY_hierarchical_identifier" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control LPAREN DUMMY_hierarchical_identifier" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control {KW_STRONG, KW_WEAK} LPAREN" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control DUMMY_event_control {KW_STRONG, KW_WEAK}" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control {KW_NEXTTIME, KW_S_NEXTTIME} KW_EVENTUALLY" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_NOT KW_EVENTUALLY" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control LPAREN KW_EVENTUALLY" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control DUMMY_event_control {KW_NEXTTIME, KW_S_NEXTTIME}" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_FIRST_MATCH LPAREN" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control {KW_NEXTTIME, KW_S_NEXTTIME} LBRACK" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control {KW_NEXTTIME, KW_S_NEXTTIME} KW_NOT" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_NOT KW_NOT" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control LPAREN KW_NOT" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_ALWAYS LBRACK" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control {KW_NEXTTIME, KW_S_NEXTTIME} KW_S_EVENTUALLY" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_NOT KW_S_EVENTUALLY" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control LPAREN KW_S_EVENTUALLY" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control {KW_ACCEPT_ON, KW_REJECT_ON, KW_SYNC_ACCEPT_ON..KW_SYNC_REJECT_ON} LPAREN" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_ALWAYS KW_NOT" using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): ru\ispras\verilog\parser\grammar\SvaParser.g:367:7:
Decision can match input such as "DUMMY_event_control KW_S_EVENTUALLY KW_NOT" using multiple alternatives: 1, 2
...
Actions #1

Updated by Mikhail Lebedev almost 4 years ago

  • Status changed from New to Resolved

Warnings are ok :)
There is some ambiguity in the grammar.

Actions #2

Updated by Sergey Smolov almost 4 years ago

Can this ambiguity be fixed or it comes from the standard?

Actions #3

Updated by Mikhail Lebedev almost 4 years ago

From the standard and because of the ANTLR features.

Actions #4

Updated by Sergey Smolov almost 4 years ago

Could these warnings be suppressed?

Actions #5

Updated by Mikhail Lebedev almost 4 years ago

No. If you look more carefully, there are also old warnings in VerilogParser.

Actions #6

Updated by Sergey Smolov over 3 years ago

  • Status changed from Resolved to Closed
  • Published in build set to 0.1.3-beta-201002
Actions

Also available in: Atom PDF