similar to: [LLVMdev] Summer of Code ideas —— reducing memory access latency

I know pc-lint is working fine on detecting some nasty coding fault. But is it illegal implement it in clang? And also there is so much other tools for code analyze:) 2010/3/26, yiqiuping1986 <yiqiuping1986 at 126.com>: > 呵呵，不急，还有一学期的时间。 > > > 2010-03-26 > > > > yiqiuping1986 > > > > 发件人： 罗勇刚(Yonggang Luo) > 发送时间： 2010-03-26 15:05:33 > 收件人：

Hi, dear LLVMers I am Qiuping Yi. I am interested in John's SoC project idea, developing Clang's support for detecting undefined behaviors in C/C++, and hope John to be my mentor. I wish to implement detecting some undefined behaivors ranging from easy (such as detecting divide by zero) to rather troublesome ones (such as detecting references to out-of-scope automatic variables). I

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

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,

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:

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:

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

John, Many thanks for your prompt reply! You think it a better idea than a new implementation of bounds overflow checking, that integrating previous work such as this: http://llvm.org/pubs/2006-05-24-SAFECode-BoundsCheck.html into current LLVM. Yes? 在 2010年3月31日 下午12:11，John Regehr <regehr at cs.utah.edu>写道： > Hi Qiuping, > > I don't know much about SAFECode, you should

Hi, John I have modified my proposal based on your suggestion. Wellcom your comments! The URL of my proposal is: http://socghop.appspot.com/gsoc/student_proposal/private/google/gsoc2010/easyqiu/t127038894856 Best Regards! Qiuping 2010-04-08 yiqiuping1986 -------------- next part -------------- An HTML attachment was scrubbed... URL:

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, 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

Hi, I intend to participate in Google's Summer of Code this year, so I'd like to bounce another idea around to see what you guys think. (I posted a similar message to cfe-dev just now.) Be warned: this will shock you. It may even horrify you. 1. Implement a 16-bit x86 backend. (*Chris recoils in horror*) Yeah, I know 16-bit x86 is dead, but I find it interesting for historical purposes

On Mar 22, 2010, at 4:34 PM, Nick Frolov wrote: >> There is a high maintenance cost to having backends in the tree (every >> codegen change requires updating all backends). Adding stuff that >> noone uses and can barely test is not goodness. > > So, proposing a backend for an unpopular architecture is not a good idea > for GSoC project in general? We generally prefer

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

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

易秋萍 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

Is anyone interested in a SoC project to further develop Clang's support for detecting undefined behaviors in C/C++? This is actually a collection of many smaller projects ranging from very easy (detecting divide by zero) to rather nasty (detecting references to out-of-scope automatic variables). If someone does this, I'm happy to help mentor, provide test cases, etc. If done well,