From: Pavel Roskin <proski@gnu.org>
To: linux-sparse@vger.kernel.org, Christopher Li <sparse@chrisli.org>
Subject: Re: Fun with Linux 2.6.21-rc1
Date: Fri, 23 Feb 2007 14:59:26 -0500 [thread overview]
Message-ID: <1172260766.14431.3.camel@dv> (raw)
In-Reply-To: <1172251518.6229.6.camel@dv>
On Fri, 2007-02-23 at 12:25 -0500, Pavel Roskin wrote:
> Hello!
>
> The current sparse reports many errors with Linux 2.6.21-rc1. There are
> screenfuls of errors for every file. I have reduced one of them to this
> simple file:
>
> struct st {
> char c;
> } __attribute__ ((aligned(2)));
> struct st s1;
> struct st s2;
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.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-02-23 19:59 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 [this message]
2007-02-23 22:30 ` [PATCH] " Christopher Li
2007-02-24 1:53 ` 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=1172260766.14431.3.camel@dv \
--to=proski@gnu.org \
--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).