From: David Laight <david.laight.linux@gmail.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Alexandre Chartre <alexandre.chartre@oracle.com>,
Nathan Chancellor <nathan@kernel.org>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
peterz@infradead.org, llvm@lists.linux.dev
Subject: Re: [PATCH v6 11/30] objtool: Trace instruction state changes during function validation
Date: Tue, 2 Dec 2025 18:09:07 +0000 [thread overview]
Message-ID: <20251202180907.169ba703@pumpkin> (raw)
In-Reply-To: <gl5aug2lwyhjyp2adwjtomxodxixqbpzxj3bcbnimfzo3xmce5@tvpxxghlmxif>
On Tue, 2 Dec 2025 08:13:21 -0800
Josh Poimboeuf <jpoimboe@kernel.org> wrote:
...
> The static local bothered me, I went with a different approach to move
> that variable (and its usage) to handle_insn_ops(). Will post shortly.
>
Does look a little wrong inside a recursively called function.
How does the code get on for 32bit builds?
I'd guess they have a lot less stack available?
David
prev parent reply other threads:[~2025-12-02 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251121095340.464045-1-alexandre.chartre@oracle.com>
[not found] ` <20251121095340.464045-12-alexandre.chartre@oracle.com>
2025-12-01 20:23 ` [PATCH v6 11/30] objtool: Trace instruction state changes during function validation Nathan Chancellor
2025-12-02 1:30 ` Josh Poimboeuf
2025-12-02 8:34 ` Alexandre Chartre
2025-12-02 16:13 ` Josh Poimboeuf
2025-12-02 18:09 ` David Laight [this message]
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=20251202180907.169ba703@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=alexandre.chartre@oracle.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@kernel.org \
--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