Florian Weimer wrote:
* Ben Chelf:
Right now, we're guarding access to the actual defects that we
report for a couple of reasons: (1) We think that you, as developers
of gcc, should have the chance to look at the defects we find to patch
them before random other folks get to see what we fou
* Ben Chelf:
> Right now, we're guarding access to the actual defects that we
> report for a couple of reasons: (1) We think that you, as developers
> of gcc, should have the chance to look at the defects we find to patch
> them before random other folks get to see what we found and (2) From a
>
So I'm basically asking for people who want to play around with some
cool new technology to help make source code better. If this interests
you, please feel free to reach out to me directly. And of course, if
there are other packages you care about that aren't currently on the
list, I want
On 3/5/06, Ben Chelf <[EMAIL PROTECTED]> wrote:
>Right now, we're guarding access to the actual defects that we report
> for a couple of reasons: (1) We think that you, as developers of gcc,
> should have the chance to look at the defects we find to patch them
> before random other folks get to
Hello gcc Developers,
I'm the CTO of Coverity, Inc., a company that does static source code
analysis to look for defects in code. You may have heard of us or of our
technology from its days at Stanford (the "Stanford Checker"). The
reason I'm writing is because we have set up a framework int
