From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ivan Babrou <ivan@cloudflare.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
kernel-team <kernel-team@cloudflare.com>
Subject: Re: Linux 4.19 and GCC 9
Date: Fri, 17 May 2019 11:23:02 +0200 [thread overview]
Message-ID: <20190517092302.GA5235@kroah.com> (raw)
In-Reply-To: <CANiq72muyjE3XPjmtQgJpGaqWR=YBi6KVNT3qe-EMXP7x+q_rQ@mail.gmail.com>
On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
> On Fri, May 17, 2019 at 10:51 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> > > On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra <peterz@infradead.org> wrote:
> > > >
> > > > Right; if there is anything you can reproduce on linus.git I'll happily
> > > > have a look. If it doesn't reproduce all you have to do is find the
> > > > patches that make it work and ask Greg.
> > >
> > > Just to clarify: Linus' master is clean of these issues with GCC 9.1.1.
> >
> > Great! Care to find the patches that did that work and send me the git
> > commit ids so that I can queue them up? I don't have gcc9 here yet on
> > my systems, so I can not test for this.
>
> I am unsure about the perf and the objtools parts (Peter/Josh?), but
> about the -Wmissing-attributes I cleaned, they were these:
>
> a6e60d84989f ("include/linux/module.h: copy __init/__exit attrs to
> init/cleanup_module")
That patch I applied now.
> c0d9782f5b6d ("Compiler Attributes: add support for __copy (gcc >= 9)")
This one will take some work to backport, let me see what is needed
here...
> ff98e20ef208 ("lib/crc32.c: mark crc32_le_base/__crc32c_le_base
> aliases as __pure")
I'll get to this as well.
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-17 9:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 18:54 Linux 4.19 and GCC 9 Ivan Babrou
2019-05-16 19:24 ` Miguel Ojeda
2019-05-16 20:11 ` Ivan Babrou
2019-05-16 21:20 ` Miguel Ojeda
2019-05-16 21:24 ` Ivan Babrou
2019-05-17 2:03 ` Josh Poimboeuf
2019-05-17 3:14 ` Ivan Babrou
2019-05-17 5:09 ` Greg KH
2019-05-17 7:38 ` Peter Zijlstra
2019-05-17 8:35 ` Miguel Ojeda
2019-05-17 8:51 ` Greg KH
2019-05-17 9:01 ` Miguel Ojeda
2019-05-17 9:23 ` Greg KH [this message]
2019-05-17 9:27 ` Miguel Ojeda
2019-05-17 9:42 ` Greg KH
2019-05-17 11:52 ` Greg KH
2019-05-17 9:48 ` Greg KH
2019-05-17 15:22 ` Arnaldo Carvalho de Melo
2019-05-17 17:23 ` Ivan Babrou
2019-05-17 17:37 ` Arnaldo Carvalho de Melo
2019-06-10 7:21 ` Ivan Babrou
2019-06-10 7:45 ` Greg KH
2019-06-10 9:32 ` Ignat Korchagin
2019-06-10 14:21 ` Greg KH
2019-06-10 14:42 ` Miguel Ojeda
2019-06-10 14:48 ` Greg KH
2019-06-10 15:01 ` Ignat Korchagin
2019-06-10 15:04 ` Miguel Ojeda
2019-06-10 15:14 ` Arnaldo Carvalho de Melo
2019-06-10 15:25 ` Greg KH
2019-06-10 19:14 ` Arnaldo Carvalho de Melo
2019-06-24 10:42 ` Ignat Korchagin
2019-06-25 7:50 ` Greg KH
2019-06-25 8:08 ` Greg KH
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=20190517092302.GA5235@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ivan@cloudflare.com \
--cc=jolsa@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.