linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Jiri Slaby <jslaby@suse.cz>,
	Joe Perches <joe@perches.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [jirislaby-stable:stable-3.12-queue 4592/5330] arch/um/include/shared/init.h:129:26: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__used'
Date: Wed, 20 Jul 2016 04:18:58 +0800	[thread overview]
Message-ID: <201607200454.0b8kp04y%fengguang.wu@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux-stable.git stable-3.12-queue
head:   4df2158fe690a10d115965bee2602ac8100ba9c2
commit: 1fa9b58c6284c20971a0750acb9b17b22775151d [4592/5330] compiler-gcc: integrate the various compiler-gcc[345].h files
config: um-x86_64_defconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        git checkout 1fa9b58c6284c20971a0750acb9b17b22775151d
        # save the attached .config to linux build tree
        make ARCH=um SUBARCH=x86_64

All errors (new ones prefixed by >>):

   In file included from arch/um/drivers/chan_user.h:9:0,
                    from arch/um/drivers/xterm.c:13:
>> arch/um/include/shared/init.h:129:26: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__used'
    #define __uml_setup_help __used __section(.uml.help.init)
                             ^
   arch/um/include/shared/init.h:122:37: note: in expansion of macro '__uml_setup_help'
     static const char *__uml_help_##fn __uml_setup_help = __uml_help_str_##fn
                                        ^~~~~~~~~~~~~~~~
   arch/um/include/shared/init.h:111:2: note: in expansion of macro '__uml_help'
     __uml_help(fn, help);      \
     ^~~~~~~~~~
   arch/um/drivers/xterm.c:71:1: note: in expansion of macro '__uml_setup'
    __uml_setup("xterm=", xterm_setup,
    ^~~~~~~~~~~
   arch/um/include/shared/init.h:128:26: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__used'
    #define __uml_init_setup __used __section(.uml.setup.init)
                             ^
   arch/um/include/shared/init.h:113:43: note: in expansion of macro '__uml_init_setup'
     static struct uml_param __uml_setup_##fn __uml_init_setup = { __uml_setup_str_##fn, fn }
                                              ^~~~~~~~~~~~~~~~
   arch/um/drivers/xterm.c:71:1: note: in expansion of macro '__uml_setup'
    __uml_setup("xterm=", xterm_setup,
    ^~~~~~~~~~~
   arch/um/include/shared/init.h:112:14: warning: '__uml_setup_str_xterm_setup' defined but not used [-Wunused-variable]
     static char __uml_setup_str_##fn[] __initdata = str;  \
                 ^
   arch/um/drivers/xterm.c:71:1: note: in expansion of macro '__uml_setup'
    __uml_setup("xterm=", xterm_setup,
    ^~~~~~~~~~~
   arch/um/include/shared/init.h:121:14: warning: '__uml_help_str_xterm_setup' defined but not used [-Wunused-variable]
     static char __uml_help_str_##fn[] __initdata = help;  \
                 ^
   arch/um/include/shared/init.h:111:2: note: in expansion of macro '__uml_help'
     __uml_help(fn, help);      \
     ^~~~~~~~~~
   arch/um/drivers/xterm.c:71:1: note: in expansion of macro '__uml_setup'
    __uml_setup("xterm=", xterm_setup,
    ^~~~~~~~~~~
   arch/um/drivers/xterm.c:47:19: warning: 'xterm_setup' defined but not used [-Wunused-function]
    static int __init xterm_setup(char *line, int *add)
                      ^~~~~~~~~~~

vim +129 arch/um/include/shared/init.h

^1da177e arch/um/include/init.h Linus Torvalds 2005-04-16  123  
^1da177e arch/um/include/init.h Linus Torvalds 2005-04-16  124  /*
^1da177e arch/um/include/init.h Linus Torvalds 2005-04-16  125   * Mark functions and data as being only used at initialization
^1da177e arch/um/include/init.h Linus Torvalds 2005-04-16  126   * or exit time.
^1da177e arch/um/include/init.h Linus Torvalds 2005-04-16  127   */
3ff6eecc arch/um/include/init.h Adrian Bunk    2008-01-24  128  #define __uml_init_setup	__used __section(.uml.setup.init)
3ff6eecc arch/um/include/init.h Adrian Bunk    2008-01-24 @129  #define __uml_setup_help	__used __section(.uml.help.init)
3ff6eecc arch/um/include/init.h Adrian Bunk    2008-01-24  130  #define __uml_init_call		__used __section(.uml.initcall.init)
3ff6eecc arch/um/include/init.h Adrian Bunk    2008-01-24  131  #define __uml_postsetup_call	__used __section(.uml.postsetup.init)
3ff6eecc arch/um/include/init.h Adrian Bunk    2008-01-24  132  #define __uml_exit_call		__used __section(.uml.exitcall.exit)

:::::: The code at line 129 was first introduced by commit
:::::: 3ff6eecca4e5c49a5d1dd8b58ea0e20102ce08f0 remove __attribute_used__

:::::: TO: Adrian Bunk <bunk@kernel.org>
:::::: CC: Sam Ravnborg <sam@ravnborg.org>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6010 bytes --]

                 reply	other threads:[~2016-07-19 20:14 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=201607200454.0b8kp04y%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=jslaby@suse.cz \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.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