On 5/28/19 9:39 AM, Luck, Tony wrote: >> Just out of curiosity, what caused this error? It doesn't _look_ new, >> just judging from the patch itself. Is this just a configuration that >> nobody has noticed before, or something else that changed that caused >> it to happen now? > > I'm confused by the error because I don't see it using an older (4.6.4) version > of gcc. But Randy is building with something modern and runs into it. > > So some aggressive optimization/inline? > > -Tony kbuild test robot reported the build error. It uses gcc 7.x. I am using gcc 8.1 from kernel.org crosstools. -- ~Randy
|