From: kbuild test robot <lkp@intel.com>
To: George Spelvin <lkml@sdf.org>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 153/210] lib/list_sort.c:17:36: warning: '__pure__' attribute ignored
Date: Fri, 29 Mar 2019 08:48:44 +0800 [thread overview]
Message-ID: <201903290838.0NizJhNr%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: ecb428ddd7449905d371074f509d08475eef43f0
commit: 14ce92c1cbed4da6460b285f83e2348cf2416e45 [153/210] lib/list_sort: simplify and remove MAX_LIST_LENGTH_BITS
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout 14ce92c1cbed4da6460b285f83e2348cf2416e45
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
>> lib/list_sort.c:17:36: warning: '__pure__' attribute ignored [-Wattributes]
struct list_head const *, struct list_head const *);
^~~~~~~~~
vim +/__pure__ +17 lib/list_sort.c
9
10 /*
11 * By declaring the compare function with the __pure attribute, we give
12 * the compiler more opportunity to optimize. Ideally, we'd use this in
13 * the prototype of list_sort(), but that would involve a lot of churn
14 * at all call sites, so just cast the function pointer passed in.
15 */
16 typedef int __pure __attribute__((nonnull(2,3))) (*cmp_func)(void *,
> 17 struct list_head const *, struct list_head const *);
18
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6675 bytes --]
reply other threads:[~2019-03-29 0:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201903290838.0NizJhNr%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=lkml@sdf.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