search for: staticanalysi

Gurus- Do llvm-gcc or clang provide a way to catch use-after-free types of issues? Thanks, -KC -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090512/0118d2b1/attachment.html>

...Tue, May 12, 2009 at 5:03 PM, Mark A. Lyan <omineo at gmail.com> wrote: > Gurus- > > Do llvm-gcc or clang provide a way to catch use-after-free types of issues? > llvm-gcc and clang don't. But I believe that the static analyzer has facilities for this. http://clang.llvm.org/StaticAnalysis.html -bw

I ran libguestfs through llvm+clang, today, [http://clang.llvm.org/StaticAnalysis.html] It found only two things worth changing -- neither is a real problems. Adding the noreturn makes it so the tool understands line 541 of guestfs.c is truly reachable only for non-NULL "p": 540 if (!p) g->abort_cb (); 541 memcpy (p, ptr, size); >From 41f8b506924243d4...

...right it's not an optimization, it is a bug-fixing > transformation and I wasn't really planning on being totally silent > and covert about anything I find (fixable or not). > This sounds more like something that could be added to the clang static analyzer ( http://clang.llvm.org/StaticAnalysis.html ). I'm not a big fan of the compiler changing the semantics of code that a programmer wrote. It's full of pitfalls. If, on the other hand, you can tell the programmer that there's the potential for a leak and let her determine if it's a "real" leak, that woul...

...t; with an svn revision number. Except instead of making someone set > LLVM_VERSION_INFO you modify it for them when its not set (or use > some other macro). Let's take example of checker build Ted produces on cfe-dev list. He regularly announces checker builds at http://clang.llvm.org/StaticAnalysis.html . The last one is checker-59 and it is not checker-(svn-revision- number). The build number, 59 in this example, is useful for the end user to connect the software build he received. The svn revision number is useful for the developer to track source base in svn. Usually, build number...

...n) as the build number. So that exactly as you are doing in your patch to Makefile.in, but I'm saying to use that svnversion number in the VERSUFFIX. > Let's take example of checker build Ted produces on cfe-dev list. He > regularly announces checker builds at http://clang.llvm.org/StaticAnalysis.html > . The last one is checker-59 and it is not checker-(svn-revision- > number). The build number, 59 in this example, is useful for the end > user to connect the software build he received. The svn revision > number is useful for the developer to track source base in svn. > Usua...

...of Floating Point Based Peephole Optimizations in LLVM [pdf] <http://www.cs.rutgers.edu/~santosh.nagarakatte/papers/alive-fp-sas16.pdf> *David Menendez, Santosh Nagarakatte, and Aarti Gupta *To Appear in the Proceedings of the 23rd Static Analysis Symposium (SAS 2016 <http://staticanalysis.org/sas2016/>)*, Edinburgh, September, 2016 The paper is available at http://www.cs.rutgers.edu/~santosh.nagarakatte/papers/alive-fp-sas16.pdf - *Termination-Checking for LLVM Peephole Optimizations [pdf] <http://www.cs.rutgers.edu/~santosh.nagarakatte/papers/icse2016-alive-lo...

On Mar 28, 2009, at 4:39 AM, Anthony Danalis wrote: > On Mar 27, 2009, at 9:15 PM, Dan Gohman wrote: >> >> On Mar 26, 2009, at 8:28 AM, Mihai Balint wrote: >>> This summer however, I plan to create an "optimization" that >>> automatically fixes memory leaks in programs - obviously only those >>> that can be fixed with the available information,

On Jul 9, 2008, at 6:13 PM, Devang Patel wrote: > > On Jul 9, 2008, at 6:13 PM, Tanya M. Lattner wrote: > >> >> Why not set the VERSUFFIX to be " (Based on Apple Inc. build 5555) >> (LLVM >> rXXXX)" >> >> Where you set the revision number? > > I do not want to set the revision number in a source file every time I > do 'svn

On Mar 27, 2009, at 9:15 PM, Dan Gohman wrote: > > On Mar 26, 2009, at 8:28 AM, Mihai Balint wrote: >> >> This summer however, I plan to create an "optimization" that >> automatically fixes memory leaks in programs - obviously only those >> that can be fixed with the available information, for example: > > Hello, > > This doesn't sound

On Jul 9, 2008, at 6:13 PM, Tanya M. Lattner wrote: > > Why not set the VERSUFFIX to be " (Based on Apple Inc. build 5555) > (LLVM > rXXXX)" > > Where you set the revision number? I do not want to set the revision number in a source file every time I do 'svn update' :) > We currently use LLVM_VERSION_INFO to set this sort of information > and to