similar to: [LLVMdev] summer_of_code_idea_—_checking_bounds_overflow_bugs

Hi， John Criswell！ You have said to me that SAFECode had not been maintained for several years, now I have submitted my proposal for updating the SAFCode project to the new LLVM APIs. If you are still interested in the topic and willing to guid my project, I will be very happy. Now I'm waiting for you comments. Here is my proposal:

yiqiuping1986 wrote: > Hi， John Criswell！ > You have said to me that SAFECode had not been maintained for several > years, Just to clarify, SAFECode *has* been and *is* maintained (primarily by me). The release_26 branch in the SVN repository works with LLVM 2.6, and mainline is working (with some regressions) with the upcoming LLVM 2.7. You can subscribe to the SVA Commits mailing list

John Regehr wrote: > Qiuping, > > Have you looked at what has already been done? I would expect that taking > previous work such as this: > > http://llvm.org/pubs/2006-05-24-SAFECode-BoundsCheck.html > > and integrating into current LLVM would be a better idea than starting > over. > This code is publicly available from the SAFECode project (see

Qiuping, Have you looked at what has already been done? I would expect that taking previous work such as this: http://llvm.org/pubs/2006-05-24-SAFECode-BoundsCheck.html and integrating into current LLVM would be a better idea than starting over. John On Tue, 30 Mar 2010, ??? wrote: > > Hi, > > Some days ago I am interested in detecting undefined behaviors > > in C

Hi, I am sorry that just now I give the wrong URL which is a private mood. The next URLs are right: Update the SAFCode project to the new LLVM API http://socghop.appspot.com/gsoc/student_proposal/show/google/gsoc2010/easyqiu/t127038894856 Check bounds overflow bugs in C programs based on LLVM http://socghop.appspot.com/gsoc/student_proposal/show/google/gsoc2010/easyqiu/t126993884556 ABCD:

2010-04-01 yiqiuping1986 发件人： John Criswell 发送时间： 2010-03-30 23:44:58 收件人： 易秋萍 抄送： llvmdev at cs.uiuc.edu 主题： Re: [LLVMdev] summer of code idea— checking boun ds overflow bugs 易秋萍 wrote: Hi, Some days ago I am interested in detecting undefined behaviors in C programs based on Clang. After several days’ investigation, I think checking bounds overflow bugs is more interesting,

Which compiler are you using to compile poolalloc? Looks like it doesn't support C++11 (doesn't recognize nullptr). Jingyue On Fri, Jan 30, 2015 at 8:32 PM, Qiuping Yi <yiqiuping at gmail.com> wrote: > Hi, John Criswell > > Thank you very much. > > I am installing LLVM-3.2, but I encounter the next error when carrying out > "make": > > llvm[3]:

On 1/30/15 11:32 PM, Qiuping Yi wrote: > Hi, John Criswell > > Thank you very much. > > I am installing LLVM-3.2, but I encounter the next error when carrying > out "make": Is this error occurring when compiling the version of Clang within SAFECode or standard Clang? If it's the former, you should know that you don't need to compile SAFECode to use

On 1/30/15 10:24 AM, Qiuping Yi wrote: > I am just not upgrade my LLVM. So I must use some higer LLVM version, > right? Yes. For working with poolalloc, I would recommend using LLVM 3.2 as we know poolalloc compiles with LLVM 3.2. If there's a release_29 branch for poolalloc, you could use that, but you won't get any bug fixes that we added between poolalloc 2.9 and poolalloc

Hi, Some days ago I am interested in detecting undefined behaviors in C programs based on Clang. After several days’ investigation, I think checking bounds overflow bugs is more interesting, because bounds overflow is one of the most frequently encountered errors in C programs. For example, performing pointer arithmetic without checking bounds can cause bounds overflow. To increase the

On 1/30/15 10:17 AM, Qiuping Yi wrote: > Thank you. But now I am using LLVM 2.9, so which version of > poolalloc I should use ? Why are you using LLVM 2.9? That's an old version of LLVM (even by my standards). Is there some other LLVM-based tool that requires that you use LLVM 2.9? Regards, John Criswell > > > -------------------------------------------- > Qiuping Yi

I am just not upgrade my LLVM. So I must use some higer LLVM version, right? -------------------------------------------- Qiuping Yi Institute Of Software Chinese Academy of Sciences On Fri, Jan 30, 2015 at 11:21 PM, John Criswell <jtcriswel at gmail.com> wrote: > On 1/30/15 10:17 AM, Qiuping Yi wrote: > > Thank you. But now I am using LLVM 2.9, so which version of poolalloc I

On Sat, Nov 22, 2014 at 11:09 AM, Sanjoy Das <sanjoy at playingwithpointers.com > wrote: > Hi Qiuping, > > If I'm reading the IR correctly, what you have is a > GetElementPtrConstantExpr [1]. It subclasses from llvm::Constant. > If you want the same code to handle GetElementPtrConstantExpr *and* GetElementPtrInst, you can use GEPOperator. > > Thanks, > --

Hi Michael, Thank you very much. But idx_begin/idx_end iterators can only be used through a getelementptr instruction, right? However, I think value "i32* getelementptr inbounds (%struct.Args* @globalArg, i64 0, i32 2)" itself is not a getelementptr instruction, so? Or could you tell me how can I get a getelementptr instruction first from this value?

So, I won't know the called function statically, Right? -------------------------------------------- Qiuping Yi Institute Of Software Chinese Academy of Sciences On Wed, Jan 20, 2016 at 2:24 PM, Nema, Ashutosh <Ashutosh.Nema at amd.com> wrote: > Typically for C++ virtual function you will see an indirect callSite > (unless not de-virtualized). > > > > Regards, >

Thank you. But now I am using LLVM 2.9, so which version of poolalloc I should use ? -------------------------------------------- Qiuping Yi Institute Of Software Chinese Academy of Sciences On Fri, Jan 30, 2015 at 11:12 PM, John Criswell <jtcriswel at gmail.com> wrote: > Dear Qiuping, > > If you use the release_32 branch of poolalloc, then you need to use LLVM > 3.2. >

Hi, John Criswell Thank you very much. I am installing LLVM-3.2, but I encounter the next error when carrying out "make": llvm[3]: Compiling ClangASTNodesEmitter.cpp for Release+Asserts build ClangASTNodesEmitter.cpp: In member function ‘std::pair<llvm::Record*, llvm::Record*><unnamed>::ClangASTNodesEmitter::EmitNode(const std::multimap<llvm::Record*, llvm::Record*,

易秋萍 wrote: > > Hi, > > Some days ago I am interested in detecting undefined behaviors > > in C programs based on Clang. After several days’ investigation, I think > > checking bounds overflow bugs is more interesting, because bounds > > overflow is one of the most frequently encountered errors in C programs. > > For example, performing pointer arithmetic without

Dear Qiuping, If you use the release_32 branch of poolalloc, then you need to use LLVM 3.2. For directions on compiling poolalloc with LLVM 3.2, please the SAFECode build directions at http://safecode.cs.illinois.edu/docs/Install.html. You can just skip the steps in the directions that compile SAFECode. Regards, John Criswell On 1/30/15 10:05 AM, Qiuping Yi wrote: > Hi, all > > I

Dear Ashutosh, Thank you, I can handle some indirect callSites by getFunction() of InvokInst and CallInst. However, when I am handling C++ programs, I found the calls of member functions are converted to some strange indirect calls. For example: table->truncate(sysTransaction); // from mysql are translated to the next complex llvm IR: _ZN8Database20getSystemTransactionEv.exit: ;