From: Randy Dunlap <rdunlap@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: Tree for Apr 3 (objtool)
Date: Fri, 5 Apr 2019 13:53:27 -0700 [thread overview]
Message-ID: <15ed85f4-bf2e-da91-71c1-46875d1c6e3f@infradead.org> (raw)
In-Reply-To: <9e4eb742-f306-7aea-a3d7-9abbb244bb55@infradead.org>
On 4/4/19 1:51 PM, Randy Dunlap wrote:
> On 4/4/19 10:16 AM, Josh Poimboeuf wrote:
>> On Wed, Apr 03, 2019 at 03:29:17PM -0700, Randy Dunlap wrote:
>>> On 4/3/19 1:53 PM, Josh Poimboeuf wrote:
>>>> On Wed, Apr 03, 2019 at 08:02:43AM -0700, Randy Dunlap wrote:
>>>>> On 4/3/19 1:24 AM, Stephen Rothwell wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Changes since 20190402:
>>>>>>
>>>>>
>>>>> on x86_64:
>>>>>
>>>>> arch/x86/entry/entry_64.o: warning: objtool: .entry.text+0x909: unreachable instruction
>>>>
>>>> Your .o file looks odd. I can't recreate the issue when I build the
>>>> same object.
>>>
>>> This (randconfig) build has tracing enabled? Could that have anything to do
>>> with it?
>>
>> No, I can't see any reasonable explanation for it other than a buggy
>> toolchain.
>>
>>> The randconfig file is attached.
>>
>> I still can't recreate with your randconfig.
>>
>>>> Did the issue only just now show up? Can you bisect it? What version
>>>> of binutils are you using?
>>>
>>>> ld -v
>>> GNU ld (GNU Binutils; openSUSE Leap 42.3) 2.31.1.20180828-19
>>>
>>>
>>> My build logs show it first occurred (in my randconfig builds) in
>>> linux-next-20190204.
>>
>> It seems really odd. Can you do a bisect?
>>
>
> Sure, I'll give it a try.
>
That didn't work very well. First I narrowed the problem down to between
4.16 (good) and 4.17-rc1 (bad), then I did the git bisects, and ended up
pointing to a SCSI driver patch.
I'm inclined to suspect that it's a padding problem, i.e. toolchain problem
like you suggested.
--
~Randy
next prev parent reply other threads:[~2019-04-05 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 8:24 linux-next: Tree for Apr 3 Stephen Rothwell
2019-04-03 15:02 ` linux-next: Tree for Apr 3 (objtool) Randy Dunlap
2019-04-03 20:53 ` Josh Poimboeuf
2019-04-03 22:29 ` Randy Dunlap
2019-04-04 17:16 ` Josh Poimboeuf
2019-04-04 20:51 ` Randy Dunlap
2019-04-05 20:53 ` Randy Dunlap [this message]
2019-04-03 15:20 ` linux-next: Tree for Apr 3 (acpi_dev_get_first_match*) Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15ed85f4-bf2e-da91-71c1-46875d1c6e3f@infradead.org \
--to=rdunlap@infradead.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).