Re: new objtool warnings again...

On Mon, Sep 26, 2016 at 01:49:14PM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Sep 23, 2016 at 02:19:04PM -0700, Linus Torvalds escreveu: > > On Fri, Sep 23, 2016 at 2:16 PM, Josh Poimboeuf wrote: > > > > > > I just started seeing this problem today. I suspect it's a

Re: new objtool warnings again...

On Mon, Sep 26, 2016 at 01:49:14PM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Sep 23, 2016 at 02:19:04PM -0700, Linus Torvalds escreveu: > > On Fri, Sep 23, 2016 at 2:16 PM, Josh Poimboeuf wrote: > > > > > > I just started seeing this problem today. I suspect it's a ccache > > > issue,

Re: new objtool warnings again...

Em Fri, Sep 23, 2016 at 02:19:04PM -0700, Linus Torvalds escreveu: > On Fri, Sep 23, 2016 at 2:16 PM, Josh Poimboeuf wrote: > > > > I just started seeing this problem today. I suspect it's a ccache > > issue, since it only showed up after ccache was updated. > > Ahh, I

Re: new objtool warnings again...

Em Fri, Sep 23, 2016 at 02:19:04PM -0700, Linus Torvalds escreveu: > On Fri, Sep 23, 2016 at 2:16 PM, Josh Poimboeuf wrote: > > > > I just started seeing this problem today. I suspect it's a ccache > > issue, since it only showed up after ccache was updated. > > Ahh, I didn't even notice that

Re: new objtool warnings again...

On Fri, Sep 23, 2016 at 2:16 PM, Josh Poimboeuf wrote: > > I just started seeing this problem today. I suspect it's a ccache > issue, since it only showed up after ccache was updated. Ahh, I didn't even notice that ccache got updated, but yeah, that makes sense.

Re: new objtool warnings again...

On Fri, Sep 23, 2016 at 2:16 PM, Josh Poimboeuf wrote: > > I just started seeing this problem today. I suspect it's a ccache > issue, since it only showed up after ccache was updated. Ahh, I didn't even notice that ccache got updated, but yeah, that makes sense. Linus

Re: new objtool warnings again...

On Fri, Sep 23, 2016 at 2:14 PM, Josh Poimboeuf wrote: > > Is this with your latest pushed master branch? I have F24, but I don't > see the warning. It is with the latest branch, but I was wrong - it doesn't show up for "allmodconfig", it only shows up for my fairly-minimal

Re: new objtool warnings again...

On Fri, Sep 23, 2016 at 2:14 PM, Josh Poimboeuf wrote: > > Is this with your latest pushed master branch? I have F24, but I don't > see the warning. It is with the latest branch, but I was wrong - it doesn't show up for "allmodconfig", it only shows up for my fairly-minimal config on this

Re: new objtool warnings again...

On Fri, Sep 23, 2016 at 02:06:03PM -0700, Linus Torvalds wrote: > On Fri, Sep 23, 2016 at 1:33 PM, Linus Torvalds > wrote: > > > > So this code is clearly missing the magic to tell gcc that the asm > > needs a frame pointer. > > Independently of that, the objtool

Re: new objtool warnings again...

On Fri, Sep 23, 2016 at 02:06:03PM -0700, Linus Torvalds wrote: > On Fri, Sep 23, 2016 at 1:33 PM, Linus Torvalds > wrote: > > > > So this code is clearly missing the magic to tell gcc that the asm > > needs a frame pointer. > > Independently of that, the objtool build seems racy or somehow >

Re: new objtool warnings again...

On Fri, Sep 23, 2016 at 01:33:45PM -0700, Linus Torvalds wrote: > Josh, > > the current F24 toolchain causes > > kernel/signal.o: warning: objtool: .altinstr_replacement+0x54: > call without frame pointer save/setup > > during a regular allmodconfig build. > > Doing an objdump says: > >

Re: new objtool warnings again...

On Fri, Sep 23, 2016 at 01:33:45PM -0700, Linus Torvalds wrote: > Josh, > > the current F24 toolchain causes > > kernel/signal.o: warning: objtool: .altinstr_replacement+0x54: > call without frame pointer save/setup > > during a regular allmodconfig build. > > Doing an objdump says: > >

Re: new objtool warnings again...

On Fri, Sep 23, 2016 at 1:33 PM, Linus Torvalds wrote: > > So this code is clearly missing the magic to tell gcc that the asm > needs a frame pointer. Independently of that, the objtool build seems racy or somehow fragile. I've now twice gotten into a situation

Re: new objtool warnings again...

On Fri, Sep 23, 2016 at 1:33 PM, Linus Torvalds wrote: > > So this code is clearly missing the magic to tell gcc that the asm > needs a frame pointer. Independently of that, the objtool build seems racy or somehow fragile. I've now twice gotten into a situation where I end up getting cat:

new objtool warnings again...

Josh, the current F24 toolchain causes kernel/signal.o: warning: objtool: .altinstr_replacement+0x54: call without frame pointer save/setup during a regular allmodconfig build. Doing an objdump says: ... 54: e8 00 00 00 00 callq 59 <.altinstr_replacement+0x59>

new objtool warnings again...

Josh, the current F24 toolchain causes kernel/signal.o: warning: objtool: .altinstr_replacement+0x54: call without frame pointer save/setup during a regular allmodconfig build. Doing an objdump says: ... 54: e8 00 00 00 00 callq 59 <.altinstr_replacement+0x59>