Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

Dear Anne,
Thank you very much for your prompt reply.

Indeed. The Locations.zones are obtained after the value analysis.
In debugging level, I find the slicing request consume much more time than
the value analysis.

I add select many Locations.zones for applying a slicing request. So i
doubt whether i add more zones?
While slicing many zones, it will divide those zones individually and
perform slicing then combine those slices together?

Thanks.

Best regards,
David Yang

On 23 September 2013 14:27, Anne Pacalet <anne.pacalet at free.fr> wrote:

> Hi,
>
> Le 23/09/2013 04:31, David Yang a ?crit :
>
>  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;
>>
>> But this is very slow, even the function is less than 20 source lines of
>> code.
>>
>
> The slicing computation needs the PDG, which needs the value analysis
> results.
> I think that if you didn't compute the value analysis before,
> the slicing plug-in run it for you, but because this computation
> is application wide, it can take some time, whatever slicing request you
> want.
>
> Maybe you would prefer to first run the value analysis, and save the
> results,
> before trying to computes slices ?
>
> Hope this helps.
> Best regards,
>
> Anne.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20130923/aca22686/attachment.html>