From: Pavel Roskin <proski@gnu.org>
To: linux-sparse@vger.kernel.org
Subject: [RFC PATCH] Fix crash in linearize_compound_statement()
Date: Mon, 07 Apr 2008 16:45:11 -0400 [thread overview]
Message-ID: <1207601111.22430.28.camel@dv> (raw)
Hello!
The current sparse crashes on this program:
static int x;
static inline void foo(void)
{
if (x)
x = 1;
}
static void bar(void)
{
foo();
}
static typeof(bar) quux;
The crash happens in linearize_compound_statement(), and I believe that
the reason is incorrect access to phi_node->phi_list without making sure
that phi_node->opcode is OP_PHI. When processing the above program,
phi_node->phi_list can be OP_INLINED_CALL.
I understand very little in sparse code, and I have no idea what kind of
fallback is needed when phi_node->opcode is not OP_PHI.
But this patch fixes the crash:
diff --git a/linearize.c b/linearize.c
index 8a68f05..ff4f3b6 100644
--- a/linearize.c
+++ b/linearize.c
@@ -1633,7 +1633,7 @@ static pseudo_t linearize_compound_statement(struct entrypoint *ep, struct state
struct basic_block *bb = add_label(ep, ret);
struct instruction *phi_node = first_instruction(bb->insns);
- if (!phi_node)
+ if (!phi_node || phi_node->opcode != OP_PHI)
return pseudo;
if (pseudo_list_size(phi_node->phi_list)==1) {
--
Regards,
Pavel Roskin
next reply other threads:[~2008-04-07 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 20:45 Pavel Roskin [this message]
2008-04-07 21:55 ` [RFC PATCH] Fix crash in linearize_compound_statement() Christopher Li
2008-04-08 5:14 ` Pavel Roskin
2008-04-08 6:05 ` 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=1207601111.22430.28.camel@dv \
--to=proski@gnu.org \
--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).