| From: | Mark Wong <markw(at)osdl(dot)org> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: sparse (static analyzer) report |
| Date: | 2005-01-13 23:09:19 |
| Message-ID: | 20050113150919.A20721@osdl.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 13, 2005 at 08:06:23PM -0300, Alvaro Herrera wrote:
> On Thu, Jan 13, 2005 at 01:31:36PM -0800, Mark Wong wrote:
> > We've also started automating sparse analyses in our PLM tool, which
> > will show an error and warning count. Here's an example:
> > http://www.osdl.org/plm-cgi/plm?module=patch_info&patch_id=4065
>
> I took a peek at the first sparse report you posted, and it's too noisy
> to be useful. The parser seems confused in several ways in thousands of
> places.
>
> Maybe there's something useful to be extracted, but we'd need to adapt
> sparse.
>
It might not have helped to dump every source file's report into a
single file. Would it have helped to split out the results per file?
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2005-01-13 23:14:43 | Re: Slow PL/pgSQL 8.0.RC5 (7.4.6. 3times faster) |
| Previous Message | Alvaro Herrera | 2005-01-13 23:06:23 | Re: sparse (static analyzer) report |