From: Christopher Li <sparse@chrisli.org>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-sparse@vger.kernel.org, Josh Triplett <josh@freedesktop.org>
Subject: [PATCH] Re: Fun with Linux 2.6.21-rc1
Date: Fri, 23 Feb 2007 14:30:27 -0800 [thread overview]
Message-ID: <20070223223027.GA5671@chrisli.org> (raw)
In-Reply-To: <1172260766.14431.3.camel@dv>
On Fri, Feb 23, 2007 at 02:59:26PM -0500, Pavel Roskin wrote:
> P.S. The breakage has nothing to do to Linux changes. It was caused by
> the patch called "Make the ptrlist using the sparse allocator". Undoing
> the patch fixes the problem.
>
No, that was not it. The bug does not trigger if I remove "-O" or remove
the recent struct attribute patch.
You make me guilt for 5 mins. But the real bugs is match_idents did not
end with NULL.
This patch should fix it:
Chris
Fix a bug that match_idents forget to end with NULL
Pavel Roskin manage to hit this bug with
struct st {
char c;
} __attribute__ ((aligned(2)));
struct st s1;
struct st s2;
Signed-Off-By: Christopher Li <sparse@chrisli.org>
Index: sparse/parse.c
===================================================================
--- sparse.orig/parse.c 2007-02-23 14:33:28.000000000 -0800
+++ sparse/parse.c 2007-02-23 14:36:16.000000000 -0800
@@ -861,7 +861,7 @@ static struct token *handle_attributes(s
apply_ctype(token->pos, &thistype, ctype);
continue;
}
- if (match_idents(token, &asm_ident, &__asm_ident, &__asm___ident)) {
+ if (match_idents(token, &asm_ident, &__asm_ident, &__asm___ident, NULL)) {
struct expression *expr;
token = expect(token->next, '(', "after asm");
token = parse_expression(token->next, &expr);
next prev parent reply other threads:[~2007-02-23 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 17:25 Fun with Linux 2.6.21-rc1 Pavel Roskin
2007-02-23 19:59 ` Pavel Roskin
2007-02-23 22:30 ` Christopher Li [this message]
2007-02-24 1:53 ` [PATCH] " Pavel Roskin
2007-02-25 22:45 ` exposing __attribute__ portability macros in lib.h; any objections? Josh Triplett
2007-02-26 10:43 ` 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=20070223223027.GA5671@chrisli.org \
--to=sparse@chrisli.org \
--cc=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.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).