linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	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>
Subject: Re: [PATCH] Raise the minimum required gcc version to 4.6
Date: Thu, 23 Aug 2018 23:52:40 +0200	[thread overview]
Message-ID: <CAMuHMdXPFgp5sLR5-UExEvxNbKSR5H--dk7KMit_XFSFN+1uHw@mail.gmail.com> (raw)
In-Reply-To: <da5620dc7a2b9d33f2a0dd7f4dc3afdab5a66f26.1534795606.git.joe@perches.com>

Hi Joe,

On Mon, Aug 20, 2018 at 10:15 PM Joe Perches <joe@perches.com> wrote:
> Various architectures fail to build properly with older versions
> of the gcc compiler.
>
> An example from Guenter Roeck via this thread:
> https://lore.kernel.org/lkml/20180814170904.GA12768@roeck-us.net/
>
> ----------------------
> In file included from ./include/linux/mm.h:17:0,
>                  from ./include/linux/pid_namespace.h:7,
>                  from ./include/linux/ptrace.h:10,
>                  from arch/openrisc/kernel/asm-offsets.c:32:
> ./include/linux/mm_types.h:497:16: error: flexible array member in otherwise empty struct
>
> This is just an example with gcc 4.5.1 for or32. I have seen the problem
> with gcc 4.4 (for unicore32) as well.
> ----------------------
>
> So update the minimum required version of gcc to 4.6.
>
> Miscellanea:
>
> o Update Documentation/process/changes.rst
> o Remove and consolidate version test blocks in compiler-gcc.h
>   for versions lower than 4.6
>
> Signed-off-by: Joe Perches <joe@perches.com>
> Reviewed-by: Kees Cook <keescook@chromium.org>
> Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>

Thanks for your patch!

I'm willing to upgrade. But there's one thing that's holding me back.

Does gcc 8.x gives again the same warnings as my venerable old gcc 4.1.2,
that no one else seems to see? Or will the real bugs I detect this way stay
unfixed? Polyculture is a good thing, also in compilers.

Reverted locally (incl. the follow-up), applied Andrew's fix, detected new
warnings in v4.18+, and sent patches where it makes sense...

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

  parent reply	other threads:[~2018-08-23 21:52 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 [this message]
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

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=CAMuHMdXPFgp5sLR5-UExEvxNbKSR5H--dk7KMit_XFSFN+1uHw@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@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).