linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <ddrake@brontes3d.com>
To: linux-sparse@vger.kernel.org
Subject: __attribute__ annotations and struct types
Date: Wed, 14 Feb 2007 15:01:54 -0500	[thread overview]
Message-ID: <1171483314.14504.9.camel@systems03.mmm.com> (raw)

gcc-4.1.1 accepts this as valid code:

struct __attribute__((__aligned__(16))) foo {
    int a;
};

sparse doesn't like it:

	test.c:7:8: error: Trying to use reserved word '__attribute__' 
	as identifier

I'm not sure if this is a bug that people are interested in solving, as
the more common form works in both gcc and sparse:

struct foo {
    int a;
} __attribute__((__aligned__(16)));

Thanks,
-- 
Daniel Drake
Brontes Technologies, A 3M Company

             reply	other threads:[~2007-02-14 20:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 20:01 Daniel Drake [this message]
2007-02-14 20:15 ` [PATCH] Re: __attribute__ annotations and struct types Christopher Li
2007-02-14 21:02   ` Daniel Drake
2007-02-14 21:05     ` Randy Dunlap
2007-02-23  2:23     ` Josh Triplett

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=1171483314.14504.9.camel@systems03.mmm.com \
    --to=ddrake@brontes3d.com \
    --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).