linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Pavel Roskin <proski@gnu.org>
Cc: Josh Triplett <josh@freedesktop.org>,
	linux-sparse <linux-sparse@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] ignore __cold__ attribute
Date: Tue, 22 Apr 2008 15:25:06 +0200	[thread overview]
Message-ID: <1208870706.31429.23.camel@johannes.berg> (raw)
In-Reply-To: <20080422090739.2izftuclwocs80o4-cebfxv@fcnzpbc.arg@webmail.spamcop.net>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

On Tue, 2008-04-22 at 09:07 -0400, Pavel Roskin wrote:
> Quoting Johannes Berg <johannes@sipsolutions.net>:
> 
> > This is a new attribute in gcc 4.3, which when used and sparse is
> > compiled with gcc 4.3 leads to unknown attribute errors. Ignore it.
> 
> According to  
> http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html, the new  
> attributes are "cold" and "hot".  I think we need them ignored both  
> with and without underscores.
> 
> The attributes indicate whether the function is likely to be executed,  
> and thus affect optimization.  There is nothing useful for sparse in  
> that information.

*Shrug*. I just wanted the kernel to work again and failed (in about 20
minutes of searching) to find a changelog for gcc mentioning this so
gave up and just added the one that the kernel uses. Want to amend the
patch?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2008-04-22 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 10:41 [PATCH] ignore __cold__ attribute Johannes Berg
     [not found] ` <20080422090739.2izftuclwocs80o4-cebfxv@fcnzpbc.arg@webmail.spamcop.net>
2008-04-22 13:25   ` Johannes Berg [this message]
2008-04-22 21:35     ` Pavel Roskin
2008-04-25  2:26       ` Josh Triplett
2008-05-02 19:42         ` Pavel Roskin
2008-06-19  5:04         ` Pavel Roskin

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=1208870706.31429.23.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=dwmw2@infradead.org \
    --cc=josh@freedesktop.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=proski@gnu.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 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).