linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
	Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: arcml <linux-snps-arc@lists.infradead.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Build regressions/improvements in v5.10-rc1
Date: Tue, 27 Oct 2020 01:45:38 +0000	[thread overview]
Message-ID: <c235619b-d4be-e064-c74a-ea67a5d70bcd@synopsys.com> (raw)
In-Reply-To: <CAMuHMdXbsJPnsXg6bA_e32zJkBG1Zzqj-ja5WzHDKL0d9OcfPg@mail.gmail.com>

Hi Geert,

On 10/26/20 2:48 AM, Geert Uytterhoeven wrote:
> On Mon, Oct 26, 2020 at 10:46 AM Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> Below is the list of build error/warning regressions/improvements in
>> v5.10-rc1[1] compared to v5.9[2].
>>
>> Summarized:
>>   - build errors: +3/-7
>>   - build warnings: +26/-28
>>
>>
>>   + {standard input}: Error: inappropriate arguments for opcode 'adc':  => 170
> arc-gcc10/axs101_defconfig

Thx for bringing this to our notice. Alexey / Claudiu - are we testing gcc-10 for
ARC700 - It seemsv5.10-rcX kerne is unearthing some sort of compiler issue

http://kisskb.ellerman.id.au/kisskb/branch/linus/head/3650b228f83adda7e5ee532e2b90429c03f7b9ec/
http://kisskb.ellerman.id.au/kisskb/target/189425/
http://kisskb.ellerman.id.au/kisskb/buildresult/14384487/log/

-------->

# < make -s -j 24 ARCH=arc O=/kisskb/build/linus_axs101_defconfig_arc-gcc10 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-10.1.0-nolibc/arc-linux/bin/arc-linux-  help
# make -s -j 24 ARCH=arc O=/kisskb/build/linus_axs101_defconfig_arc-gcc10 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-10.1.0-nolibc/arc-linux/bin/arc-linux-  olddefconfig
# make -s -j 24 ARCH=arc O=/kisskb/build/linus_axs101_defconfig_arc-gcc10 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-10.1.0-nolibc/arc-linux/bin/arc-linux-  
{standard input}: Assembler messages:
{standard input}:170: Error: inappropriate arguments for opcode 'adc'
make[2]: *** [/kisskb/src/scripts/Makefile.build:283: fs/remap_range.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/kisskb/src/Makefile:1799: fs] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:185: __sub-make] Error 2
Command 'make -s -j 24 ARCH=arc O=/kisskb/build/linus_axs101_defconfig_arc-gcc10 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-10.1.0-nolibc/arc-linux/bin/arc-linux-  ' returned non-zero exit status 2
# rm -rf /kisskb/build/linus_axs101_defconfig_arc-gcc10
# Build took: 0:01:21.179119

_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

      parent reply	other threads:[~2020-10-27  1:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201026081811.3934205-1-geert@linux-m68k.org>
2020-10-26  9:48 ` Build regressions/improvements in v5.10-rc1 Geert Uytterhoeven
2020-10-26 10:17   ` Christopher Obbard
2020-10-27  1:45   ` Vineet Gupta [this message]

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=c235619b-d4be-e064-c74a-ea67a5d70bcd@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=Claudiu.Zissulescu@synopsys.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).