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 found and (2) From a
support perspective, we want to make sure that we have the appropriate
time to engage with those who want to use the results to fix the
code.
Will the unedited results of the first run be made public after some
time period, so that we can judge the quality of your tool? 8-)
>
This is the first request I've had for this particular viewing of the
results. What we have in place now is certainly a first step in
providing access to the community -- depending on response (which has
been very good thus far!), we'll have to figure out what the next best
step is for granting people access to what we find. In general though,
the results are much better if some people take a bit of time to comb
through some, suggest configuration to reduce false positives, and so on...
-ben
