[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a0BUDCUE7qT=tAh4U2LNOqHUBDadRJXsbJMT3cX3hnVnQ@mail.gmail.com>
Date: Wed, 1 Mar 2017 16:27:29 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Denys Vlasenko <dvlasenk@...hat.com>
Subject: Re: [PATCH] [RFC] x86: avoid -mtune=atom for objtool warnings
On Wed, Mar 1, 2017 at 3:40 PM, Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> On Wed, Mar 01, 2017 at 10:45:03AM +0100, Arnd Bergmann wrote:
>> Actually, something must have changed in gcc since last month, I also
>> just got a report in another file:
>>
>> drivers/i2c/busses/i2c-img-scb.o: warning: objtool: img_i2c_probe()
>> falls through to next function img_i2c_read_fifo()
>
> This one looks like it could be related to some recent objtool changes
> which affect how it interprets 'ud2'. Which commit were you testing
> with? Can you provide the .config file, and the object file if it's not
> too big?
This is with my randconfig test series on top of latest linux-next.
I see it with the latest gcc-7.0.1 snapshot as well as an earlier gcc-7.0.0
build (20161201), but not with gcc-6.3.1
Arnd
Download attachment "i2c-img-scb.o" of type "application/x-object" (15088 bytes)
Download attachment "0xE4B9EB4B_defconfig.gz" of type "application/x-gzip" (23060 bytes)
Powered by blists - more mailing lists