From: Christopher Li <sparse@chrisli.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Hannes Eder <hannes@hanneseder.net>,
linux-sparse@vger.kernel.org,
Nicholas Mc Guire <der.herr@hofr.at>
Subject: Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
Date: Mon, 23 Mar 2009 02:22:47 -0700 [thread overview]
Message-ID: <70318cbf0903230222q3546233cn39071f19ab956f2c@mail.gmail.com> (raw)
In-Reply-To: <20090321172823.GA5509@ZenIV.linux.org.uk>
>
> It needed testing, all right - #elif handling got broken by the initial
> variant... Hopefully fixed version follows:
Looks good. BTW, it is simpler than my version which try to do
the processor in argument list.
Applied, thanks.
Chris
prev parent reply other threads:[~2009-03-23 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 13:49 [bug, bisected, -chrisl] Segfault at evaluate.c:341 Hannes Eder
2009-03-19 14:46 ` Al Viro
2009-03-19 18:32 ` Nicholas Mc Guire
2009-03-19 18:38 ` Hannes Eder
2009-03-19 19:14 ` Al Viro
2009-03-19 20:04 ` Christopher Li
2009-03-19 21:52 ` Al Viro
2009-03-19 22:09 ` Al Viro
2009-03-19 23:11 ` Christopher Li
2009-03-21 4:40 ` Al Viro
2009-03-21 17:28 ` Al Viro
2009-03-23 9:22 ` Christopher Li [this message]
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=70318cbf0903230222q3546233cn39071f19ab956f2c@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=der.herr@hofr.at \
--cc=hannes@hanneseder.net \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.