This is the mail archive of the cygwin-developers mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Clang static analyzer results


On Mon, 2012-07-02 at 16:04 -0400, Christopher Faylor wrote: 
> On Fri, Jan 27, 2012 at 04:56:41AM -0600, Yaakov (Cygwin/X) wrote:
> >I just added the clang-analyzer to the pending LLVM/Clang ITP, and what
> >better way to test it than on the Cygwin codebase itself.  Here are the
> >results for CVS HEAD as of yesterday:
> >
> >http://cygwin-ports.sourceforge.net/scan-build/
> >
> Many months later, I thought maybe the above might have uncovered
> something which would shed some light on the stack problems that I
> noted.  It didn't but I did take a swing through this report and
> eliminated some of the more obvious issues.
> 
> Any chance, you could rerun this Yaakov?

Done and uploaded to the same location.

> I promise to look at it within the next three months if so.  That 
> will more than half the amount of time it took me to look at your
> last report.

:-)

> Btw, Clang doesn't actually build a usable version of Cygwin does it?

I haven't tried yet.  Clang didn't handle PE C++ exceptions as of 3.0:

http://cygwin.com/ml/cygwin/2012-02/msg00025.html

But the bugzilla entry mentioned there seems to indicate that 3.1 might
work.  If I can get my other llvm-dependent packages to build with 3.1,
I'll give it a shot when I have a chance.


Yaakov



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]