mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Nathan Chancellor <nathan@kernel.org>,
	loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] objtool/LoongArch: Fix unreachable instruction warnings about head.S
Date: Tue, 26 Aug 2025 20:30:23 +0800	[thread overview]
Message-ID: <b7551efd-cb5b-7503-c455-b8f22fac81bd@loongson.cn> (raw)
In-Reply-To: <CAAhV-H7NNtH-oaqMsN5=2c+EdF0-dy5mxcsO=_KFGWqb-FZj_w@mail.gmail.com>

On 2025/8/26 下午4:26, Huacai Chen wrote:
> On Tue, Aug 26, 2025 at 2:46 PM Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
>>
>> When compiling with LLVM and CONFIG_LTO_CLANG is set, there exist the
>> following objtool warnings after silencing all of the other warnings:

...

>>   arch/loongarch/kernel/head.S | 8 ++++----
>>   1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/loongarch/kernel/head.S b/arch/loongarch/kernel/head.S
>> index e3865e92a917..566a1dbf5fa0 100644
>> --- a/arch/loongarch/kernel/head.S
>> +++ b/arch/loongarch/kernel/head.S
>> @@ -20,6 +20,7 @@
>>          __HEAD
>>
>>   _head:
>> +       UNWIND_HINT_UNDEFINED
>>          .word   IMAGE_DOS_SIGNATURE     /* "MZ", MS-DOS header */
>>          .org    0x8
>>          .dword  _kernel_entry           /* Kernel entry point (physical address) */
>> @@ -30,6 +31,7 @@ _head:
>>          .long   pe_header - _head       /* Offset to the PE header */
>>
>>   pe_header:
>> +       UNWIND_HINT_UNDEFINED
>>          __EFI_PE_HEADER
> The efi header is completely not code, the annotations are very strange.

Yes, I think so too, but the aim is only to not checking for objtool,
it seems no other better way.

Thanks,
Tiezhu


  reply	other threads:[~2025-08-26 12:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26  6:46 [RFC PATCH 0/2] Fix objtool warnings if LTO is enabled for LoongArch (Part 2) Tiezhu Yang
2025-08-26  6:46 ` [RFC PATCH 1/2] objtool/LoongArch: Fix fall through warning about efi_boot_kernel() Tiezhu Yang
2025-08-26  8:32   ` Huacai Chen
2025-08-26 12:33     ` Tiezhu Yang
2025-08-26 13:03       ` Huacai Chen
2025-08-26 23:39         ` Josh Poimboeuf
2025-08-28  2:01           ` Tiezhu Yang
2025-08-26  6:46 ` [RFC PATCH 2/2] objtool/LoongArch: Fix unreachable instruction warnings about head.S Tiezhu Yang
2025-08-26  8:20   ` Peter Zijlstra
2025-08-26 12:27     ` Tiezhu Yang
2025-08-26  8:26   ` Huacai Chen
2025-08-26 12:30     ` Tiezhu Yang [this message]
2025-08-26 23:43       ` Josh Poimboeuf
2025-08-28  2:01         ` Tiezhu Yang

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=b7551efd-cb5b-7503-c455-b8f22fac81bd@loongson.cn \
    --to=yangtiezhu@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®