public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "dan carpenter" <error27@email.com>
To: green@namesys.com
Cc: linux-kernel@vger.kernel.org, smatch-discuss@lists.sf.net
Subject: Re: smatch update / 2.5.64 / kbugs.org
Date: Fri, 07 Mar 2003 03:32:25 -0500	[thread overview]
Message-ID: <20030307083226.12083.qmail@email.com> (raw)

From: Oleg Drokin <green@namesys.com>
 
> Also is anybody working on "redundant assignments" stuff as described in Standford guys papers?
> 
 
I have been planning to write an equivelence module that
would save what variables where equivelent.  For example ...
a = b = kmalloc();
c = a;
... a, b and c are all equivelent.

The redundant assignment check looks for places that 
assign a variable to an equivelent variable.  You would 
need to check for this anyway as part of writing the 
equivelence module.

The equivelence module has other uses as well ...
a = b = kmalloc();
if (!a) {
        return -ENOMEM;
}
b->foo = bar;

Right now the dereference check prints a false positive
on those, but the equivelence module would fix that.

I don't have the "redundant code" paper in front of me, 
so I forget what other types of things they looked for.

regards,
dan carpenter

-- 
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Meet Singles
http://corp.mail.com/lavalife


             reply	other threads:[~2003-03-07  8:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07  8:32 dan carpenter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-07  6:45 smatch update / 2.5.64 / kbugs.org dan carpenter
2003-03-07  6:53 ` Oleg Drokin
2003-03-14  8:25   ` Oleg Drokin
2003-03-06  8:15 dan carpenter
2003-03-06  7:37 dan carpenter
2003-03-06  7:42 ` Greg KH
2003-03-06 15:37 ` Oleg Drokin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030307083226.12083.qmail@email.com \
    --to=error27@email.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smatch-discuss@lists.sf.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox