From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 219192] drivers/iio/imu/adis16400.o: warning: objtool: adis16400_write_raw() falls through to next function adis16400_show_flash_count()
Date: Sun, 06 Oct 2024 19:51:26 +0000 [thread overview]
Message-ID: <bug-219192-217253-dr3tSMZ9VE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219192-217253@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219192
--- Comment #8 from Andy Shevchenko (andy.shevchenko@gmail.com) ---
(In reply to Tudor Gheorghiu from comment #6)
> I saw this bugreport and I must say I encountered a somewhat similar but
> not quite the same warning message from objtool when compiling with
> clang.
>
> This is my environment:
> Linux version 6.12.0-rc1+ (Ubuntu clang version 18.1.3 (1ubuntu1), Ubuntu
> LLD 18.1.3)
>
> This is the objtool warning:
> > drivers/iio/imu/adis16400.o: warning: objtool: adis16400_write_raw+0x89:
> > can't find jump dest instruction at .text+0x8be
>
> I dissasembled the binary and this is what I found at that offset:
> > 0x0000000000000781 <+113>: jmp 0x8a4 <adis16400_write_raw+404>
> > 0x0000000000000786 <+118>: mov %rdi,%r12
> > 0x0000000000000789 <+121>: lea 0x30(%r14),%rdi
> > 0x000000000000078d <+125>: call 0x792 <adis16400_write_raw+130>
> > 0x0000000000000792 <+130>: mov %r14,%rbx
> > 0x0000000000000795 <+133>: add $0x30,%rbx
> > 0x0000000000000799 <+137>: je 0x8be
>
> Looking at .text+0x8be:
> > (gdb) x/4i 0x00000000000008be+0x8be
> > 0x117c <adis16300_channels+1180>: add %al,(%rax)
How did you get 0x117c? It can't be correct offset AFAIU all this.
> > 0x117e <adis16300_channels+1182>: add %al,(%rax)
> > 0x1180 <adis16300_channels+1184>: add $0x0,%al
> > 0x1182 <adis16300_channels+1186>: add %al,(%rax)
The above looks to me like a data or so. But I don't remember by heart the
actual binary codes for these assembly to be sure.
> I cannot tell if this is an actual issue, or just a false positive,
> but I decided to post my findings here nevertheless.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-10-06 19:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 9:35 [Bug 219192] New: drivers/iio/imu/adis16400.o: warning: objtool: adis16400_write_raw() falls through to next function adis16400_show_flash_count() bugzilla-daemon
2024-08-25 9:35 ` [Bug 219192] " bugzilla-daemon
2024-08-26 10:11 ` [Bug 219192] New: " Jonathan Cameron
2024-08-26 10:11 ` [Bug 219192] " bugzilla-daemon
2024-09-09 14:31 ` bugzilla-daemon
2024-09-09 18:56 ` Jonathan Cameron
2024-09-09 18:56 ` bugzilla-daemon
2024-09-10 5:42 ` bugzilla-daemon
2024-09-14 11:37 ` Jonathan Cameron
2024-09-14 11:37 ` bugzilla-daemon
2024-10-02 21:24 ` bugzilla-daemon
2024-10-06 10:49 ` Jonathan Cameron
2024-10-06 10:49 ` bugzilla-daemon
2024-10-06 19:51 ` bugzilla-daemon [this message]
2024-10-18 11:02 ` bugzilla-daemon
2024-10-18 17:39 ` Jonathan Cameron
2024-10-18 17:39 ` bugzilla-daemon
2025-01-23 17:45 ` bugzilla-daemon
2025-01-25 11:39 ` Jonathan Cameron
2025-01-25 11:39 ` bugzilla-daemon
2025-04-30 6:33 ` bugzilla-daemon
2025-05-05 12:02 ` Jonathan Cameron
2025-05-05 12:02 ` bugzilla-daemon
2026-03-17 16:42 ` bugzilla-daemon
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=bug-219192-217253-dr3tSMZ9VE@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.