mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	arcml <linux-snps-arc@lists.infradead.org>,
	Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
Subject: Re: Build regressions/improvements in v5.6
Date: Mon, 30 Mar 2020 18:25:18 -0700	[thread overview]
Message-ID: <a5e8ec79-2eff-7517-4b90-38d5cb366f45@roeck-us.net> (raw)
In-Reply-To: <c8447243-98c6-d545-9766-e6b3f33f4d13@synopsys.com>

On 3/30/20 2:17 PM, Vineet Gupta wrote:
> On 3/30/20 1:40 PM, Alexey Brodkin wrote:
>> Hi Andy, Geert,
>>
>>> -----Original Message-----
>>> From: Andy Shevchenko <andy.shevchenko@gmail.com>
>>> Sent: Monday, March 30, 2020 4:28 PM
>>> To: Geert Uytterhoeven <geert@linux-m68k.org>; Alexey Brodkin <abrodkin@synopsys.com>
>>> Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
>>> Subject: Re: Build regressions/improvements in v5.6
>>>
>>> On Mon, Mar 30, 2020 at 4:26 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>>>>
>>>> Hi Andy,
>>>>
>>>> On Mon, Mar 30, 2020 at 3:08 PM Andy Shevchenko
>>>> <andy.shevchenko@gmail.com> wrote:
>>>>> On Mon, Mar 30, 2020 at 12:00 PM Geert Uytterhoeven
>>>>> <geert@linux-m68k.org> wrote:
>>>>>> Below is the list of build error/warning regressions/improvements in
>>>>>> v5.6[1] compared to v5.5[2].
>>>>>
>>>>>>   + /kisskb/src/include/linux/dev_printk.h: warning: format '%zu' expects argument of type
>>> 'size_t', but argument 8 has type 'unsigned int' [-Wformat=]:  => 232:23
>>>>>
>>>>> This is interesting... I checked all dev_WARN_ONCE() and didn't find an issue.
>>>>
>>>> arcv2/axs103_smp_defconfig
>>>>
>>>> It's probably due to a broken configuration for the arc toolchain.
>>>
>>> Alexey, do have any insight?
>>
>> I think I do have some but first I'd like to get it reproduced myself.
>> I just built v5.6 with help of both GCC 8.3.1- & 9.3.1-based toolchains
>> and didn't see a single warning. So I guess I was doing something wrong.
>>
>> FWIW
>>
>> 1. My GCC 8.3.1 toolchain was exactly this:
>> https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/download/arc-2019.09-release/arc_gnu_2019.09_prebuilt_uclibc_le_archs_linux_install.tar.gz
>>
>> 2. Linux kernel is vanilla v5.6.0
>>
>> 3. Configured and built as simple as:
>>    make axs103_smp_defconfig && make
> 
> It seems the build service is using a arc toolchain built in 2016 :-)
> 
> # < /opt/cross/kisskb/br-arcle-hs38-full-2016.08-613-ge98b4dd/bin/arc-linux-gcc
> 
> Call it Murphy's law, same year a little later I'd fixed the same issue in gcc [1]
> 
> [1] http://lists.infradead.org/pipermail/linux-snps-arc/2016-October/001661.html
> 
> @Guenter could you please consider updating the ARC tools. FWIW you can build
> stuff off upstream gcc/binutils using build system of your choice.
> 

I am currently using vanilla gcc 9.2.0 to build arc and arcv2 images. Are you saying
that I need to update to gcc 9.3.0 ? gcc 9.3.0 was released only a couple of weeks
ago. I don't usually jump onto new compiler releases that quickly because each
release tends to have regressions.

[ Never mind, I just noticed Geert's reply. Still.... ]

Guenter

  parent reply	other threads:[~2020-03-31  1:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30  8:58 Geert Uytterhoeven
2020-03-30  9:05 ` Geert Uytterhoeven
2020-03-30 13:08 ` Andy Shevchenko
2020-03-30 13:26   ` Geert Uytterhoeven
2020-03-30 13:28     ` Andy Shevchenko
2020-03-30 20:40       ` Alexey Brodkin
2020-03-30 21:17         ` Vineet Gupta
2020-03-30 21:22           ` Geert Uytterhoeven
2020-03-31  1:25           ` Guenter Roeck [this message]
2020-03-31  1:43             ` Vineet Gupta

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=a5e8ec79-2eff-7517-4b90-38d5cb366f45@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=Eugeniy.Paltsev@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=andy.shevchenko@gmail.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

all inboxes | Powered by JetHome®