From: Josh Triplett <josht@linux.vnet.ibm.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: linux-sparse@vger.kernel.org, Robin Getz <rgetz@blackfin.uclinux.org>
Subject: Re: specifying custom attributes
Date: Thu, 02 Aug 2007 17:53:04 -0700 [thread overview]
Message-ID: <1186102384.3081.39.camel@josh-work.beaverton.ibm.com> (raw)
In-Reply-To: <8bd0f97a0708021553m6edaefccof086012f64b199a3@mail.gmail.com>
On Thu, 2007-08-02 at 18:53 -0400, Mike Frysinger wrote:
> the Blackfin port has a few custom gcc attributes that annoys sparse:
> include/asm/uaccess.h:63:77: error: attribute 'l1_text': unknown attribute
>
> is there a way from the cmdline to specify a custom list of OK
> attributes ? i feel like adding these processor-specific attributes
> to the source code may not be the way you guys wish to go ...
Currently no. It might make sense to add a way to turn off the "unknown
attribute" warning, like GCC's -Wno-attributes.
- Josh Triplett
next prev parent reply other threads:[~2007-08-03 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 22:53 specifying custom attributes Mike Frysinger
2007-08-03 0:53 ` Josh Triplett [this message]
2007-08-03 3:41 ` Robin Getz
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=1186102384.3081.39.camel@josh-work.beaverton.ibm.com \
--to=josht@linux.vnet.ibm.com \
--cc=linux-sparse@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.org \
--cc=vapier.adi@gmail.com \
/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).