mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	Luca Barbieri <luca@luca-barbieri.com>
Subject: lib/atomic64_test.c:107:2: error: implicit declaration of function 'atomic64_add_unless'
Date: Sun, 12 Jun 2016 01:52:19 +0800	[thread overview]
Message-ID: <201606120116.LNFqH02C%fengguang.wu@intel.com> (raw)

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

Hi,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   3d0f0b6a5520878305589411b8d434fe088e4f21
commit: 86a8938078a8bb518c5376de493e348c7490d506 lib: Add self-test for atomic64_t
date:   6 years ago
config: frv-allmodconfig (attached as .config)
compiler: frv-linux-gcc (GCC) 4.9.0
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 86a8938078a8bb518c5376de493e348c7490d506
        # save the attached .config to linux build tree
        make.cross ARCH=frv 

All errors (new ones prefixed by >>):

   lib/atomic64_test.c: In function 'test_atomic64':
>> lib/atomic64_test.c:107:2: error: implicit declaration of function 'atomic64_add_unless' [-Werror=implicit-function-declaration]
     BUG_ON(!atomic64_add_unless(&v, one, v0));
     ^
   lib/atomic64_test.c:116:2: error: implicit declaration of function 'atomic64_dec_if_positive' [-Werror=implicit-function-declaration]
     BUG_ON(atomic64_dec_if_positive(&v) != (onestwos - 1));
     ^
>> lib/atomic64_test.c:129:2: error: implicit declaration of function 'atomic64_inc_not_zero' [-Werror=implicit-function-declaration]
     BUG_ON(atomic64_inc_not_zero(&v));
     ^
   cc1: some warnings being treated as errors

vim +/atomic64_add_unless +107 lib/atomic64_test.c

   101	
   102		INIT(v0);
   103		BUG_ON(atomic64_cmpxchg(&v, v2, v1) != v0);
   104		BUG_ON(v.counter != r);
   105	
   106		INIT(v0);
 > 107		BUG_ON(!atomic64_add_unless(&v, one, v0));
   108		BUG_ON(v.counter != r);
   109	
   110		INIT(v0);
   111		BUG_ON(atomic64_add_unless(&v, one, v1));
   112		r += one;
   113		BUG_ON(v.counter != r);
   114	
   115		INIT(onestwos);
   116		BUG_ON(atomic64_dec_if_positive(&v) != (onestwos - 1));
   117		r -= one;
   118		BUG_ON(v.counter != r);
   119	
   120		INIT(0);
   121		BUG_ON(atomic64_dec_if_positive(&v) != -one);
   122		BUG_ON(v.counter != r);
   123	
   124		INIT(-one);
   125		BUG_ON(atomic64_dec_if_positive(&v) != (-one - one));
   126		BUG_ON(v.counter != r);
   127	
   128		INIT(onestwos);
 > 129		BUG_ON(atomic64_inc_not_zero(&v));
   130		r += one;
   131		BUG_ON(v.counter != r);
   132	

---
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: 23446 bytes --]

                 reply	other threads:[~2016-06-11 17:45 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=201606120116.LNFqH02C%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca@luca-barbieri.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

all inboxes | Powered by JetHome®