Project

General

Profile

Actions

Feature #7304

closed

Allow users to reject verification objects of large sizes

Added by Evgeny Novikov about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Urgent
Category:
Program fragments generation
Target version:
-
Start date:
06/20/2016
Due date:
% Done:

0%

Estimated time:
Published in build:
753dd6b

Description

We already realized that large modules are hard to prepare for verification and to verify. In particular they usually require very much resources for all non-trivial cases. Sometimes it even can prevent other modules from checking, e.g. due to hang ups and resource exhausting.

Instead of investigating some implicit ways to reject such the modules, we decided to supply a new straightforward option that will allow to reject corresponding verification objects early if their LOCs exceed the specified maximum one. Then we will have more chances to verify all modules even after some changes in tools/specifications.

To have a way to experiment with these large modules nevertheless it has sense to support the supplementary option that reject verification objects that occupies less LOCs that the minimum one.


Related issues 2 (0 open2 closed)

Blocked by Klever - Feature #7303: Calculate sizes of module source code and show them in BridgeClosedAlexey Polushkin06/20/2016

Actions
Blocks Klever - Feature #7327: Experiment with large modulesRejected06/22/2016

Actions
Actions

Also available in: Atom PDF