From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Joe Perches <joe@perches.com>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Mike Galbraith <efault@gmx.de>,
Guenter Roeck <linux@roeck-us.net>,
Rik van Riel <riel@surriel.com>,
Kees Cook <keescook@chromium.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Jonathan Corbet <corbet@lwn.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [PATCH] Raise the minimum required gcc version to 4.6
Date: Tue, 8 Jan 2019 15:09:42 +0100 [thread overview]
Message-ID: <CAMuHMdV9W4hDeVW2=jP0YN1vF1mjbr0-4nrcLWi=H1mR214EtQ@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdW1OqswdSRj2DROFST46dLCmMU5=ki2x0FBn8OjJjgLdg@mail.gmail.com>
On Sat, Dec 29, 2018 at 3:25 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Fri, Aug 24, 2018 at 12:00 AM Joe Perches <joe@perches.com> wrote:
> > On Thu, 2018-08-23 at 23:52 +0200, Geert Uytterhoeven wrote:
> > > Reverted locally (incl. the follow-up), applied Andrew's fix, detected new
> > > warnings in v4.18+, and sent patches where it makes sense...
> >
> > Thanks for that.
>
> Given the rise of anonymous unions all over the place, I gave up, and
> have upgraded from gcc 4.1.2 to 7.3.0 for cross-compiling m68k kernels.
> One good things is that the kernel size for an atari_defconfig kernel dropped
> by 3.7% or 163 KiB.
>
> For the record, below is a list of differences in generated warnings.
> Note that the source trees are not identical, as the tree used with
> gcc-7.3.0 did not include any workarounds I needed for gcc-4.1.2.
> All warnings flagged by gcc 4.1.2 should be false positives (iff I did a
> good job during the last few years ;-)
>
> I plan to repeat the exercise with gcc-8.2.0 (after v4.21-rc1 or so).
As promised, gcc-7.3.0 => gcc-8.2.0:
*** ERRORS ***
4 error regressions:
+ error: devfreq.c: undefined reference to `strcmp': => .text+0x9c6)
+ error: ldm.c: undefined reference to `strcmp': =>
.text+0x1900), .text+0x1964), .text+0x19a0), .text+0x193c)
+ error: proc.c: undefined reference to `strcmp': =>
.text+0x18c), .text+0x178)
+ error: xattr.c: undefined reference to `strcmp': =>
.text+0xbaa), .text+0xbf0), .text+0x2e8), .text+0x268), .text+0x97a),
.text+0x9be), .text+0x3d4)
Hmm, time to fix the auto-strncmp-to-strcmp-conversion for good...
*** WARNINGS ***
1 warning regressions:
+ drivers/dio/dio.c: warning: ‘strcpy’ writing 69 or more bytes
into a region of size 64 overflows the destination
[-Wstringop-overflow=]: => 240:17
That's a nice one, it found a 15 year old bug. Patch sent ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2019-01-08 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 20:15 [PATCH] Raise the minimum required gcc version to 4.6 Joe Perches
2018-08-20 20:25 ` Nick Desaulniers
2018-08-20 20:42 ` Jonathan Corbet
2018-08-20 20:48 ` Joe Perches
2018-08-21 6:55 ` Masahiro Yamada
2018-08-21 19:40 ` Linus Torvalds
2018-08-21 23:41 ` Nick Desaulniers
2018-08-23 21:52 ` Geert Uytterhoeven
2018-08-23 22:00 ` Nick Desaulniers
2018-08-23 22:00 ` Joe Perches
2018-12-29 14:25 ` Geert Uytterhoeven
2018-12-29 21:57 ` Arnd Bergmann
2019-01-08 14:09 ` Geert Uytterhoeven [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='CAMuHMdV9W4hDeVW2=jP0YN1vF1mjbr0-4nrcLWi=H1mR214EtQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=efault@gmx.de \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux@roeck-us.net \
--cc=ndesaulniers@google.com \
--cc=riel@surriel.com \
--cc=torvalds@linux-foundation.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).