Project

General

Profile

Actions

Bug #9173

closed

Incorrect DataType: BIT_VECTOR(1) instead of BIT_VECTOR(40)

Added by Sergey Smolov over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
High
Target version:
Start date:
07/27/2018
Due date:
% Done:

0%

Estimated time:
Detected in build:
master
Platform:
Published in build:

Description

VeriTrans calculates wrong DataType for 'scr_reg' variable of 'parse_pack_header' module that is attached (see "Retrascope MC Benchmark" for more details).

The correct type should be BIT_VECTOR(40), but now it is BIT_VECTOR(1).


Files

parsepack.v (1.7 KB) parsepack.v Sergey Smolov, 07/27/2018 05:24 PM

Related issues 1 (0 open1 closed)

Related to Retrascope Test Suite - Bug #9172: Texas97ParsepackCfgGraphMlTestCase: ru.ispras.retrascope.basis.exception.RetrascopeException: Wrong range: 0 < 0 or 7 > 1.ClosedSergey Smolov07/27/2018

Actions
Actions #1

Updated by Sergey Smolov over 6 years ago

  • Related to Bug #9172: Texas97ParsepackCfgGraphMlTestCase: ru.ispras.retrascope.basis.exception.RetrascopeException: Wrong range: 0 < 0 or 7 > 1. added
Actions #2

Updated by Sergey Smolov over 6 years ago

Actions #3

Updated by Sergey Smolov over 6 years ago

  • Priority changed from Normal to High
Actions #4

Updated by Alexander Kamkin about 6 years ago

It seems that the elaborator extracts type from the output declaration, which is incomplete.

...
output scr_reg;
...
reg[39:0] scr_reg;
...
Actions #5

Updated by Alexander Kamkin about 6 years ago

  • Status changed from New to Resolved

Merging namesake declarations has been added.

Actions #6

Updated by Sergey Smolov about 6 years ago

  • Status changed from Resolved to Verified
Actions #7

Updated by Sergey Smolov about 6 years ago

  • Status changed from Verified to Closed
Actions

Also available in: Atom PDF