From: Uros Bizjak <ubizjak@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>, Josh Poimboeuf <jpoimboe@kernel.org>
Cc: linux-kernel@vger.kernel.org,
tip-bot2 for Josh Poimboeuf <tip-bot2@linutronix.de>,
linux-tip-commits@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Brian Gerst <brgerst@gmail.com>,
x86@kernel.org
Subject: Re: [tip: x86/asm] x86/asm: Make ASM_CALL_CONSTRAINT conditional on frame pointers
Date: Tue, 4 Mar 2025 16:28:54 +0100 [thread overview]
Message-ID: <3102a67f-f18e-33c6-4301-4ab4df4db003@gmail.com> (raw)
In-Reply-To: <959B2AE8-109C-4EAD-A977-8EBAFD8A1075@zytor.com>
On 4. 03. 25 00:59, H. Peter Anvin wrote:
> On March 3, 2025 2:45:48 PM PST, Josh Poimboeuf <jpoimboe@kernel.org> wrote:
>> On Mon, Mar 03, 2025 at 02:31:50PM -0800, H. Peter Anvin wrote:
>>>> +#ifdef CONFIG_UNWINDER_FRAME_POINTER
>>>> #define ASM_CALL_CONSTRAINT "r" (__builtin_frame_address(0))
>>>> +#else
>>>> +#define ASM_CALL_CONSTRAINT
>>>> +#endif
>>>>
>>>> #endif /* __ASSEMBLY__ */
>>>>
>>>
>>> Wait, why was this changed? I actually tested this form at least once
>>> and found that it didn't work under all circumstances...
>>
>> Do you have any more details about where this didn't work? I tested
>> with several configs and it seems to work fine. Objtool will complain
>> if it doesn't work.
>>
>> See here for the justification (the previous version was producing crap
>> code in Clang):
>>
>> https://lore.kernel.org/dbea2ae2fb39bece21013f939ddeb15507baa7d3.1740964309.git.jpoimboe@kernel.org
>>
>
> I need to dig it up, but I had a discussion about this with some gcc people about a year ago.
It was discussed here [1].
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117311
Uros.
next prev parent reply other threads:[~2025-03-04 15:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 11:02 [tip: x86/asm] x86/asm: Make ASM_CALL_CONSTRAINT conditional on frame pointers tip-bot2 for Josh Poimboeuf
2025-03-03 18:28 ` Linus Torvalds
2025-03-03 22:37 ` Josh Poimboeuf
2025-03-04 8:33 ` Ingo Molnar
2025-03-04 17:51 ` Linus Torvalds
2025-03-04 18:01 ` Linus Torvalds
2025-03-04 18:21 ` Josh Poimboeuf
2025-03-04 18:48 ` Linus Torvalds
2025-03-04 18:57 ` Linus Torvalds
2025-03-04 19:56 ` Josh Poimboeuf
2025-03-04 20:09 ` Josh Poimboeuf
2025-03-04 20:13 ` Linus Torvalds
2025-03-04 20:25 ` Linus Torvalds
2025-03-04 20:41 ` Linus Torvalds
2025-03-04 22:45 ` Josh Poimboeuf
2025-03-04 19:47 ` Josh Poimboeuf
2025-03-04 20:00 ` Josh Poimboeuf
2025-03-04 19:15 ` Ingo Molnar
2025-03-03 22:31 ` H. Peter Anvin
2025-03-03 22:45 ` Josh Poimboeuf
2025-03-03 22:47 ` Josh Poimboeuf
2025-03-04 0:35 ` H. Peter Anvin
2025-03-04 0:57 ` Andrew Cooper
2025-03-04 2:05 ` H. Peter Anvin
2025-03-04 17:45 ` Josh Poimboeuf
2025-03-04 15:35 ` Uros Bizjak
2025-03-04 22:08 ` H. Peter Anvin
2025-03-03 23:59 ` H. Peter Anvin
2025-03-04 15:28 ` Uros Bizjak [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-04 10:36 tip-bot2 for Josh Poimboeuf
2025-03-07 22:04 ` H. Peter Anvin
2025-03-07 23:05 ` Ingo Molnar
2025-03-07 23:21 ` Josh Poimboeuf
2025-03-07 23:29 ` H. Peter Anvin
2025-03-08 1:38 ` Josh Poimboeuf
2025-03-08 8:15 ` David Laight
2025-03-08 17:06 ` Josh Poimboeuf
2025-03-10 14:49 ` H. Peter Anvin
2025-03-13 23:33 ` Josh Poimboeuf
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=3102a67f-f18e-33c6-4301-4ab4df4db003@gmail.com \
--to=ubizjak@gmail.com \
--cc=brgerst@gmail.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tip-bot2@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox