linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jacek Śliwerski" <sliwers@googlemail.com>
To: linux-sparse@vger.kernel.org
Subject: Re: Defect in linearization of short circuit &&
Date: Sun, 14 Feb 2010 22:04:29 +0100	[thread overview]
Message-ID: <4B78655D.2080007@googlemail.com> (raw)
In-Reply-To: <4B77FD0F.50401@googlemail.com>

Apparently, the issue is not with the linearization.  I noticed that the 
condition has been parsed as:

EXPR_BINOP
  * EXPR_LOGICAL
     * EXPR_LOGICAL
        * EXPR_PREOP
        * EXPR_PREOP
     * EXPR_COMPARE
  * EXPR_COMPARE

After replacing EXPR_BINOP with EXPR_LOGICAL in the top node of the 
tree, the linearization works just fine.  Could someone explain me the 
difference between EXPR_BINOP and EXPR_LOGICAL in this context?

Thanks!
Jacek

  reply	other threads:[~2010-02-14 21:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 13:39 Defect in linearization of short circuit && Jacek Śliwerski
2010-02-14 21:04 ` Jacek Śliwerski [this message]
2010-02-14 23:09   ` Christopher Li
2010-02-15 19:12     ` Jacek Śliwerski
2010-02-15 19:41       ` Christopher Li
2010-02-15 20:18         ` Jacek Śliwerski
2010-02-15 21:11           ` Christopher Li
2010-02-16  9:28             ` Bernd Petrovitsch
2010-02-16 19:02               ` Christopher Li
2010-02-16 19:10                 ` Christopher Li
2010-02-16 19:19                 ` Jacek Śliwerski
2010-02-16 19:36                   ` Christopher Li
2010-02-16 20:11                     ` enum warning patch (was Re: Defect in linearization of short circuit &&) Kamil Dudka
2010-02-16 20:18                       ` Kamil Dudka
2010-02-16 22:44                         ` Christopher Li
2010-02-17 14:00                           ` Kamil Dudka
2010-02-17 11:47                 ` Defect in linearization of short circuit && Bernd Petrovitsch
2010-02-17 20:22                   ` Christopher Li

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=4B78655D.2080007@googlemail.com \
    --to=sliwers@googlemail.com \
    --cc=linux-sparse@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).