From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.99]:33484 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727309AbfEQJsQ (ORCPT ); Fri, 17 May 2019 05:48:16 -0400 Date: Fri, 17 May 2019 11:48:13 +0200 From: Greg KH Subject: Re: Linux 4.19 and GCC 9 Message-ID: <20190517094813.GA15090@kroah.com> References: <20190516225013.nvhwqi5tfwtby6qb@treble> <20190517050931.GB32367@kroah.com> <20190517073813.GB2589@hirez.programming.kicks-ass.net> <20190517085126.GA3249@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Miguel Ojeda Cc: Peter Zijlstra , Ivan Babrou , Josh Poimboeuf , Ingo Molnar , Arnaldo Carvalho de Melo , Alexander Shishkin , Jiri Olsa , Namhyung Kim , linux-kernel , Linux Kbuild mailing list , kernel-team On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote: > On Fri, May 17, 2019 at 10:51 AM Greg KH 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 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") > c0d9782f5b6d ("Compiler Attributes: add support for __copy (gcc >= 9)") > ff98e20ef208 ("lib/crc32.c: mark crc32_le_base/__crc32c_le_base > aliases as __pure") This last patch is not needed, as that only resolves something that showed in in 4.20. thanks, greg k-h