From: kbuild test robot <lkp@intel.com>
To: Stefan Agner <stefan@agner.ch>
Cc: kbuild-all@01.org, linux@armlinux.org.uk,
ndesaulniers@google.com, natechancellor@gmail.com, arnd@arndb.de,
ard.biesheuvel@linaro.org, nicolas.pitre@linaro.org,
peterz@infradead.org, mingo@redhat.com, will.deacon@arm.com,
julien.thierry@arm.com, mark.rutland@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Stefan Agner <stefan@agner.ch>
Subject: Re: [PATCH 2/3] ARM: uaccess: use unified assembler language syntax
Date: Mon, 31 Dec 2018 03:30:57 +0800 [thread overview]
Message-ID: <201812310315.KnAnTpSb%fengguang.wu@intel.com> (raw)
In-Reply-To: <8190fb3605e863295bdb6311b1966b69d4fa9e73.1546185298.git.stefan@agner.ch>
[-- Attachment #1: Type: text/plain, Size: 8245 bytes --]
Hi Stefan,
I love your patch! Yet something to improve:
[auto build test ERROR on arm/for-next]
[also build test ERROR on v4.20 next-20181224]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Stefan-Agner/ARM-fix-argument-count-to-match-macro-definition/20181231-001137
base: git://git.armlinux.org.uk/~rmk/linux-arm.git for-next
config: arm-pcm027_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=arm
All errors (new ones prefixed by >>):
/tmp/ccSM947n.s: Assembler messages:
>> /tmp/ccSM947n.s:1603: Error: bad instruction `sbcscc ip,ip,r3'
>> /tmp/ccSM947n.s:2036: Error: bad instruction `sbcscc lr,lr,r3'
>> /tmp/ccSM947n.s:2079: Error: bad instruction `sbcscc r1,r1,ip'
>> /tmp/ccSM947n.s:2237: Error: bad instruction `sbcscc r4,r4,r3'
--
/tmp/ccpLxmD2.s: Assembler messages:
>> /tmp/ccpLxmD2.s:217: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccpLxmD2.s:410: Error: bad instruction `sbcscc r1,r1,ip'
>> /tmp/ccpLxmD2.s:607: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:676: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:739: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:782: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccpLxmD2.s:1058: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1095: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccpLxmD2.s:1191: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1210: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1261: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccpLxmD2.s:1313: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1361: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1410: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccpLxmD2.s:1440: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1511: Error: bad instruction `sbcscc r1,r1,r3'
>> /tmp/ccpLxmD2.s:1593: Error: bad instruction `sbcscc r2,r2,r3'
/tmp/ccpLxmD2.s:1637: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1692: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1772: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1820: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1889: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1942: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:1996: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccpLxmD2.s:2090: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccpLxmD2.s:2335: Error: bad instruction `sbcscc r1,r1,r3'
>> /tmp/ccpLxmD2.s:2542: Error: bad instruction `sbcscc r0,r0,r1'
--
/tmp/ccAjGERX.s: Assembler messages:
/tmp/ccAjGERX.s:329: Error: bad instruction `sbcscc r1,r1,r3'
>> /tmp/ccAjGERX.s:367: Error: bad instruction `sbcscc r1,r1,r0'
/tmp/ccAjGERX.s:552: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccAjGERX.s:698: Error: bad instruction `sbcscc r1,r1,r3'
--
/tmp/ccQ0YGje.s: Assembler messages:
>> /tmp/ccQ0YGje.s:864: Error: bad instruction `sbcscc ip,ip,r8'
>> /tmp/ccQ0YGje.s:3564: Error: bad instruction `sbcscc r0,r0,r2'
/tmp/ccQ0YGje.s:3603: Error: bad instruction `sbcscc r0,r0,r2'
--
/tmp/ccSrZAfg.s: Assembler messages:
/tmp/ccSrZAfg.s:595: Error: bad instruction `sbcscc ip,ip,r3'
>> /tmp/ccSrZAfg.s:893: Error: bad instruction `sbcscc r1,r1,r2'
/tmp/ccSrZAfg.s:1084: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccSrZAfg.s:1342: Error: bad instruction `sbcscc r0,r0,r2'
/tmp/ccSrZAfg.s:1379: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccSrZAfg.s:1628: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccSrZAfg.s:1697: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccSrZAfg.s:1782: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccSrZAfg.s:1827: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccSrZAfg.s:1922: Error: bad instruction `sbcscc r1,r1,r3'
--
/tmp/ccQVk2bL.s: Assembler messages:
>> /tmp/ccQVk2bL.s:339: Error: bad instruction `sbcscc r2,r2,r5'
/tmp/ccQVk2bL.s:785: Error: bad instruction `sbcscc r1,r1,r3'
--
/tmp/cctwQj9v.s: Assembler messages:
/tmp/cctwQj9v.s:3331: Error: bad instruction `sbcscc r1,r1,r2'
>> /tmp/cctwQj9v.s:3454: Error: bad instruction `sbcscc ip,ip,r1'
>> /tmp/cctwQj9v.s:3886: Error: bad instruction `sbcscc r6,r6,r3'
>> /tmp/cctwQj9v.s:4053: Error: bad instruction `sbcscc r3,r3,ip'
/tmp/cctwQj9v.s:4501: Error: bad instruction `sbcscc r1,r1,r3'
--
/tmp/ccdaVsdC.s: Assembler messages:
/tmp/ccdaVsdC.s:1040: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccdaVsdC.s:1117: Error: bad instruction `sbcscc r1,r1,r2'
/tmp/ccdaVsdC.s:1169: Error: bad instruction `sbcscc r1,r1,r2'
/tmp/ccdaVsdC.s:1490: Error: bad instruction `sbcscc ip,ip,r3'
/tmp/ccdaVsdC.s:1608: Error: bad instruction `sbcscc r2,r2,r3'
/tmp/ccdaVsdC.s:1645: Error: bad instruction `sbcscc r2,r2,r3'
/tmp/ccdaVsdC.s:2127: Error: bad instruction `sbcscc lr,lr,r3'
/tmp/ccdaVsdC.s:2178: Error: bad instruction `sbcscc r2,r2,r3'
/tmp/ccdaVsdC.s:2254: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccdaVsdC.s:3002: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccdaVsdC.s:3090: Error: bad instruction `sbcscc ip,ip,r3'
/tmp/ccdaVsdC.s:3407: Error: bad instruction `sbcscc ip,ip,r3'
>> /tmp/ccdaVsdC.s:3514: Error: bad instruction `sbcscc ip,ip,r2'
/tmp/ccdaVsdC.s:4601: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccdaVsdC.s:4903: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccdaVsdC.s:5002: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccdaVsdC.s:5357: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccdaVsdC.s:5423: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccdaVsdC.s:5482: Error: bad instruction `sbcscc r2,r2,r3'
/tmp/ccdaVsdC.s:5536: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccdaVsdC.s:5983: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccdaVsdC.s:6056: Error: bad instruction `sbcscc ip,ip,r2'
/tmp/ccdaVsdC.s:6168: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccdaVsdC.s:6226: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccdaVsdC.s:6439: Error: bad instruction `sbcscc ip,ip,r3'
/tmp/ccdaVsdC.s:6613: Error: bad instruction `sbcscc ip,ip,r3'
/tmp/ccdaVsdC.s:6653: Error: bad instruction `sbcscc r0,r0,r2'
/tmp/ccdaVsdC.s:6722: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccdaVsdC.s:6806: Error: bad instruction `sbcscc r1,r1,r3'
--
/tmp/ccETCYt7.s: Assembler messages:
>> /tmp/ccETCYt7.s:193: Error: bad instruction `sbcscc ip,ip,lr'
>> /tmp/ccETCYt7.s:870: Error: bad instruction `sbcscc r3,r3,r4'
--
/tmp/ccO4VON1.s: Assembler messages:
>> /tmp/ccO4VON1.s:661: Error: bad instruction `sbcscc r5,r5,r3'
/tmp/ccO4VON1.s:761: Error: bad instruction `sbcscc r5,r5,r3'
/tmp/ccO4VON1.s:879: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccO4VON1.s:980: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccO4VON1.s:1465: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccO4VON1.s:1618: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccO4VON1.s:1689: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/ccO4VON1.s:1768: Error: bad instruction `sbcscc r0,r0,r3'
/tmp/ccO4VON1.s:1808: Error: bad instruction `sbcscc r2,r2,r3'
--
/tmp/cc3U7xxJ.s: Assembler messages:
/tmp/cc3U7xxJ.s:284: Error: bad instruction `sbcscc ip,ip,r3'
/tmp/cc3U7xxJ.s:1487: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/cc3U7xxJ.s:1596: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/cc3U7xxJ.s:2047: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/cc3U7xxJ.s:2120: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/cc3U7xxJ.s:2352: Error: bad instruction `sbcscc r1,r1,r3'
/tmp/cc3U7xxJ.s:2617: Error: bad instruction `sbcscc r0,r0,r2'
>> /tmp/cc3U7xxJ.s:2800: Error: bad instruction `sbcscc r7,r7,r3'
..
---
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: 14447 bytes --]
next prev parent reply other threads:[~2018-12-30 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 16:08 [PATCH 0/3] ARM: trivial assembly fixes to enable LLVM as Stefan Agner
2018-12-30 16:08 ` [PATCH 1/3] ARM: fix argument count to match macro definition Stefan Agner
2018-12-30 16:08 ` [PATCH 2/3] ARM: uaccess: use unified assembler language syntax Stefan Agner
2018-12-30 19:30 ` kbuild test robot [this message]
[not found] ` <201812310309.fFJTFUuf%fengguang.wu@intel.com>
2019-01-02 15:09 ` Stefan Agner
2018-12-30 16:08 ` [PATCH 3/3] ARM: spinlock: " Stefan Agner
2018-12-30 21:27 ` kbuild test robot
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=201812310315.KnAnTpSb%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=julien.thierry@arm.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=nicolas.pitre@linaro.org \
--cc=peterz@infradead.org \
--cc=stefan@agner.ch \
--cc=will.deacon@arm.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).