From: "Jacek Śliwerski" <sliwers@googlemail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Defect in linearization of short circuit &&
Date: Mon, 15 Feb 2010 20:12:38 +0100 [thread overview]
Message-ID: <4B799CA6.70807@googlemail.com> (raw)
In-Reply-To: <70318cbf1002141509u4ebc4ef5x51ec41f5f1452a7a@mail.gmail.com>
Christopher Li pisze:
>
> EXPR_BINOP used in normal operation require two operands.
> e.g. a + b, a | b
> Both operands will get evaluated.
>
> EXPR_LOGICAL using for condition branching and it has the short curcit
> behavior in mind. e.g. a || b
I found the offending block of code. It is in expand.c, in function
expand_logical:
/*
* If the right side is safe and cheaper than a branch,
* just avoid the branch and turn it into a regular binop
* style SAFELOGICAL.
*/
if (rcost < BRANCH_COST) {
expr->type = EXPR_BINOP;
rcost -= BRANCH_COST - 1;
}
After removing these lines, everything works fine.
But I guess that there must have been a reason to add them in the first
place. I see it checking the cost of the operation, but I don't know
why somebody assumes that it would be safe not to make a branch. Does
anybody know how to fix it without simply removing these lines?
Thanks!
Jacek
next prev parent reply other threads:[~2010-02-15 19:12 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
2010-02-14 23:09 ` Christopher Li
2010-02-15 19:12 ` Jacek Śliwerski [this message]
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=4B799CA6.70807@googlemail.com \
--to=sliwers@googlemail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).