[RFC] Exposing ghccc calling convention as preserve_none to clang

weiguozhi · January 8, 2024, 10:58pm

I have sent out the following patch for review.

github.com/llvm/llvm-project

New calling convention preserve_none

llvm:main ← weiguozhi:carrot-preserve-none

opened 09:46PM - 03 Jan 24 UTC

weiguozhi

+419 -3

The new experimental calling convention preserve_none is the opposite side of ex…isting preserve_all. It tries to preserve as few general registers as possible. So all general registers are caller saved registers. It can also uses more general registers to pass arguments. This attribute doesn't impact floating-point registers. Floating-point registers still follow the c calling convention. Currently preserve_none is supported on X86-64 only. It changes the c calling convention in following fields: * RSP and RBP are the only preserved general registers, all other general registers are caller saved registers. * We can use [RDI, RSI, RDX, RCX, R8, R9, R11, R12, R13, R14, R15, RAX] to pass arguments. It can improve the performance of hot tailcall chain, because many callee saved registers' save/restore instructions can be removed if the tail functions are using preserve_none. In my experiment in protocol buffer, the parsing functions are improved by 3% to 10%.

Topic		Replies	Views
"Preserve none" calling convention Using Clang x86	1	565	June 21, 2023
Improving support for the "Cold" Calling Convention LLVM Dev List Archives	1	96	January 14, 2013
IPRA, interprocedural register allocation, question LLVM Dev List Archives	31	120	July 15, 2016
Request for merge: GHC/ARM calling convention. LLVM Dev List Archives	9	96	August 1, 2012
preserve registers across function call LLVM Dev List Archives	4	146	August 27, 2015

[RFC] Exposing ghccc calling convention as preserve_none to clang

Related topics