Content-Type: multipart/mixed; boundary="===============8672149848759193833==" MIME-Version: 1.0 From: Sami Tolvanen To: kbuild-all@lists.01.org Subject: Re: [PATCH 11/22] pci: lto: fix PREL32 relocations Date: Wed, 24 Jun 2020 16:21:37 -0700 Message-ID: <20200624232137.GA243469@google.com> In-Reply-To: List-Id: --===============8672149848759193833== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Wed, Jun 24, 2020 at 04:03:48PM -0700, Nick Desaulniers wrote: > On Wed, Jun 24, 2020 at 3:50 PM kernel test robot wrote: > > > > Hi Sami, > > > > Thank you for the patch! Perhaps something to improve: > > > > [auto build test WARNING on 26e122e97a3d0390ebec389347f64f3730fdf48f] > > > > url: https://github.com/0day-ci/linux/commits/Sami-Tolvanen/add-supp= ort-for-Clang-LTO/20200625-043816 > > base: 26e122e97a3d0390ebec389347f64f3730fdf48f > > config: i386-alldefconfig (attached as .config) > > compiler: gcc-9 (Debian 9.3.0-13) 9.3.0 > > reproduce (this is a W=3D1 build): > > # save the attached .config to linux build tree > > make W=3D1 ARCH=3Di386 > = > Note: W=3D1 ^ > = > > > > If you fix the issue, kindly add following tag as appropriate > > Reported-by: kernel test robot > > > > All warnings (new ones prefixed by >>): > > > > In file included from arch/x86/kernel/pci-dma.c:9: > > >> include/linux/compiler-gcc.h:72:45: warning: no previous prototype f= or '__UNIQUE_ID_via_no_dac190' [-Wmissing-prototypes] > > 72 | #define __UNIQUE_ID(prefix) __PASTE(__PASTE(__UNIQUE_ID_, pr= efix), __COUNTER__) > > | ^~~~~~~~~~~~ > > include/linux/pci.h:1914:7: note: in definition of macro '___DECLARE= _PCI_FIXUP_SECTION' > > 1914 | void stub(struct pci_dev *dev) { hook(dev); } \ > > | ^~~~ > = > Should `stub` be qualified as `static inline`? https://godbolt.org/z/cPBX= xW > Or should stub be declared in this header, but implemented in a .c > file? (I'm guessing the former, since the `hook` callback comes from > the macro). Does static inline guarantee that the compiler won't rename the symbol? The purpose of this change is to have a stable symbol name, which we can safely use in inline assembly. Sami --===============8672149848759193833==--