[LLVMdev] Interprocedural slicing using LLVM

[Mingliang LIU]

John,

Thanks for your quick reply.

Firstly, I'd like to employ a slicer for our benchmarking work (in one
word, reducing the long-time irrelevant computing). I find the giri project
and the LLVMSlicer[1]. However, the giri doesn't seem a complete
implementation to me. I admit that I have not finished reading
document/discussion, e.g. the previous threads in this mailing list. While
the latter has no documents/comments, which is of great importance to a
beginner.

Secondly, I'm not an actual compiler guy although I'm trying to. If any of
you who participated the giri project would like to direct me to write a
full, generic and robust slicer for LLVM, I'm more confident to work on it.

Last, in FindFlow.h:67, is the code correct? I suppose it should be:

> -   std::vector<const Function *>::iterator FE = Targets.begin();
> ---
> +   std::vector<const Function *>::iterator FE = Targets.end();


Regards.

L

[1] https://github.com/jirislaby


On Mon, Nov 19, 2012 at 1:46 PM, Mingliang LIU <liuml07 at gmail.com> wrote:

> John,
>
> Thanks for your quick reply.
>
> Firstly, I'd like to employ a slicer for our benchmarking work (in one
> word, reducing the long-time irrelevant computing). I find the giri project
> and the LLVMSlicer[1]. However, the giri doesn't seem a complete
> implementation to me. I admit that I have not finished reading
> document/discussion, e.g. the previous threads in this mailing list. While
> the latter has no documents/comments, which is of great importance to a
> beginner.
>
> Secondly, I'm not an actual compiler guy although I'm trying to. If any of
> you who participated the giri project would like to direct me to write a
> full, generic and robust slicer for LLVM, I'm more confident to work on it.
>
> Last, in FindFlow.h:67, is the code correct? I suppose it should be:
>
>> -   std::vector<const Function *>::iterator FE = Targets.begin();
>> ---
>> +   std::vector<const Function *>::iterator FE = Targets.end();
>
>
> Regards.
>
> L
>
> [1] https://github.com/jirislaby
>
>
>
> On Sun, Nov 18, 2012 at 4:19 AM, John Criswell <criswell at illinois.edu>wrote:
>
>>  On 11/17/12 6:25 AM, Mingliang LIU wrote:
>>
>> Hi,
>>
>>    1. How can I report a bug or commit a patch to the giri progject? I
>>    doubt this central commit list is the right place.
>>
>>
>> I think posting to llvmdev is fine for now.  However, I think it would be
>> better if we just gave you commit access so that you can make changes
>> directly.  Would you like commit access?
>>
>>
>>
>>    1. Are you still maintaining the giri project any more?
>>
>>
>> Well, we never really started maintaining the giri project.  We began the
>> work of releasing our code by creating the giri project and adding some of
>> our slicing code to it because people kept asking us for a copy.  We really
>> haven't started a concerted effort to make it a "real" LLVM sub-project
>> (like SAFECode, for example) because a) one of the primary contributors is
>> finishing his Ph.D., and b) we weren't sure if there was a sufficient
>> community of users that would use it and help us maintain it.
>>
>> So, if you'd like to update giri or provide bug fixes or what not, I can
>> give you commit access, and you can have at it.  The only thing we ask is
>> that the code be licensed under the University of Illinois open source
>> license (the BSD-style license that LLVM uses).
>>
>> -- John T.
>>
>>
>
>
> --
> Mingliang LIU (刘明亮 in Chinese)
>
> PACMAN Group,  Dept. of Computer Science & Technology
> Tsinghua University, Beijing 100084, China
> Email: liuml07 at mails.tsinghua.edu.cn
> Homepage: http://pacman.cs.tsinghua.edu.cn/~liuml07/
>
>


-- 
Mingliang LIU (刘明亮 in Chinese)

PACMAN Group,  Dept. of Computer Science & Technology
Tsinghua University, Beijing 100084, China
Email: liuml07 at mails.tsinghua.edu.cn
Homepage: http://pacman.cs.tsinghua.edu.cn/~liuml07/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121120/b446b079/attachment.html>