--- layout: fc_discuss_archives title: Message 120 from Frama-C-discuss on September 2013 ---
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] About the slicing plugin. (slicing speed on slicing zones)



>
> Le 23/09/2013 04:31, David Yang a ?crit :
> >* Dear all,
> *>
> >* What is the slicing algorithm for slicing zones in frama-c?
> *>
> >* Currently, I am using frama-c to perform program slicing. I am not
> *>* very sure about the slicing algorithm for slicing zones in frama-c.
> *>
> >* Firstly, I select zones (Locations.Zone.t) related to a function by
> *>* using : Db.Slicing.select_func_zone
> *>* Then, I apply the slicing request by using:
> *>* !Db.Slicing.Request.apply_all prj ~propagate_to_callers:false;
> * Setting propagate_to_callers to false gives partial results.
> >* But this is very slow, even the function is less than 20 source lines
> *>* of code.
> *The slicing relies on the results of the value analysis plugins and the
> PDG plugins.
> These analysis can also take some time to be performed since they are
> done on the whole program.
> >
> >* I guess the slicing plugin perform a slicing task in the following :
> *>* 1. Apply slicing request for each zone respectively
> *>* 2. Combine those slices related to each zone.
> *>
> >* Am I right?
> *>
> >* In addition, any suggestion on how to improve speed for this kind of
> *>* slicing task?
> *Could you identify which part of the analysis is slow using some debug
> level ?
> Patrick.


Thanks.

I select many zones for only one slicing task. Whether does it matters?
Before request a slicing task, I already have performed the value analysis.

David Yang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20130923/f1b08993/attachment-0001.html>