From: Xi Ruoyao <xry111@xry111.site>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Huacai Chen <chenhuacai@kernel.org>
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH v4 8/8] LoongArch: Add ORC stack unwinder support
Date: Mon, 23 Oct 2023 16:43:26 +0800 [thread overview]
Message-ID: <4d3363eb5f4d864cfd171d89b1a13da5ef8b784c.camel@xry111.site> (raw)
In-Reply-To: <1698048691-19521-9-git-send-email-yangtiezhu@loongson.cn>
On Mon, 2023-10-23 at 16:11 +0800, Tiezhu Yang wrote:
> +ifdef CONFIG_OBJTOOL
> +KBUILD_CFLAGS += -fno-optimize-sibling-calls -fno-jump-tables -falign-functions=4
> +endif
Why do we need to regress the code generation so much for objtool?
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-10-23 8:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 8:11 [PATCH v4 0/8] Add objtool and orc support for LoongArch Tiezhu Yang
2023-10-23 8:11 ` [PATCH v4 1/8] objtool/LoongArch: Enable objtool to be built Tiezhu Yang
2023-10-23 8:11 ` [PATCH v4 2/8] objtool/LoongArch: Implement instruction decoder Tiezhu Yang
2023-10-23 8:11 ` [PATCH v4 3/8] objtool/x86: Separate arch-specific and generic parts Tiezhu Yang
2023-10-23 8:11 ` [PATCH v4 4/8] objtool/LoongArch: Enable orc to be built Tiezhu Yang
2023-10-23 8:11 ` [PATCH v4 5/8] objtool: Check local label about sibling call Tiezhu Yang
2023-10-23 8:11 ` [PATCH v4 6/8] objtool: Check local label in add_dead_ends() Tiezhu Yang
2023-10-23 8:11 ` [PATCH v4 7/8] objtool: Check local label in read_unwind_hints() Tiezhu Yang
2023-10-23 8:11 ` [PATCH v4 8/8] LoongArch: Add ORC stack unwinder support Tiezhu Yang
2023-10-23 8:43 ` Xi Ruoyao [this message]
2023-10-23 9:21 ` Tiezhu Yang
2023-10-27 7:02 ` Huacai Chen
2023-10-27 9:25 ` Tiezhu Yang
2023-10-27 9:31 ` Huacai Chen
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=4d3363eb5f4d864cfd171d89b1a13da5ef8b784c.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenhuacai@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=peterz@infradead.org \
--cc=yangtiezhu@loongson.cn \
/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®