Project

General

Profile

Feature #6780

Implement CIF in Python (script and module)

Added by Evgeny Novikov almost 4 years ago. Updated 5 months ago.

Status:
New
Priority:
High
Category:
Core
Start date:
02/03/2016
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

At the moment different Python tools use CIF, so, best practices should be implemented in a Python library. In addition, please see https://forge.ispras.ru/issues/9346#note-3.

BTW, it has sense to specify a list of compiler options that CIF should use for preprocessing, source code querying and instrumentation (just for C-backend!) rather than a list of compiler options that are not supported by CIF.


Related issues

Related to C Instrumentation Framework - Feature #6829: Make CIF to look like GCCOpen02/09/2016

Actions
Blocked by Klever - Bug #6769: External commands failures are not included into unknown reportsClosed02/03/2016

Actions
Blocks Klever - Feature #6731: Pass source code just through C-backend if aspects are emptyNew02/03/2016

Actions
Blocks Klever - Feature #6644: Debug CIF just when debuggingNew01/29/2016

Actions

History

#1

Updated by Evgeny Novikov over 3 years ago

BTW, each plugin should provide a unique output file for CIF, e.g. some file placed into a plugin working directory, to avoid races between different plugins (CIF outputs all intermediate and output files near an output file). At the moment SA uses original output files that lead to intermediate CIF files appear near original input files.

#2

Updated by Evgeny Novikov about 2 years ago

  • Subject changed from Implement AVTG common library to invoke CIF and process its output to Implement VTG common library to invoke CIF and process its output
  • Category changed from *Abstract tasks generation to Tasks generation
#3

Updated by Evgeny Novikov about 2 years ago

Copied from the #8504 description:
When CIF failed, there are too many different errors in output log. But in fact, only first error is informative.
It is offered to show the first error and skip others.

#4

Updated by Ilja Zakharov about 2 years ago

  • Assignee set to Alexey Polushkin
  • Priority changed from Normal to Urgent
  • Target version set to 1.0
#5

Updated by Evgeny Novikov about 2 years ago

  • Assignee deleted (Alexey Polushkin)
  • Priority changed from Urgent to High
  • Target version deleted (1.0)

Indeed this isn't so important issue while #8504 is implemented without any common CIF library.

#6

Updated by Evgeny Novikov about 1 year ago

  • Priority changed from High to Urgent
  • Category deleted (Tasks generation)
  • Description updated (diff)
  • Subject changed from Implement VTG common library to invoke CIF and process its output to Implement common Python library to invoke CIF and process its output
  • Project changed from Klever to C Instrumentation Framework
#7

Updated by Evgeny Novikov 11 months ago

  • Blocks Bug #9346: Remove "-include" options after second stage added
#8

Updated by Evgeny Novikov 11 months ago

  • Description updated (diff)
  • Subject changed from Implement common Python library to invoke CIF and process its output to Implement CIF in Python (sciprt and module)
#9

Updated by Evgeny Novikov 11 months ago

  • Subject changed from Implement CIF in Python (sciprt and module) to Implement CIF in Python (script and module)
#10

Updated by Evgeny Novikov 11 months ago

  • Assignee set to Ilya Shchepetkov
  • Category set to Core

Ilya is the most appropriate developer of CIF in Python.

#11

Updated by Evgeny Novikov 6 months ago

  • Blocks deleted (Bug #9346: Remove "-include" options after second stage)
#12

Updated by Evgeny Novikov 5 months ago

  • Priority changed from Urgent to High

Although, the suggested improvement will help to several CIF users, it is not extremely important.

#13

Updated by Ilya Shchepetkov 5 months ago

Also available in: Atom PDF