Home
last modified time | relevance | path

Searched refs:sret (Results 1 – 25 of 26) sorted by relevance

12

/openbsd/sys/arch/riscv64/riscv64/
H A Dsbi.c147 struct sbi_ret sret; in sbi_init() local
153 sret = sbi_get_spec_version(); in sbi_init()
154 if (sret.error != 0) { in sbi_init()
161 sbi_spec_version = sret.value; in sbi_init()
H A Dexception.S232 sret
242 sret
249 sret
H A Ddb_instruction.h2484 DECLARE_INSN(sret, MATCH_SRET, MASK_SRET)
/openbsd/gnu/llvm/compiler-rt/lib/dfsan/
H A Ddfsan_interceptors.cpp103 INTERCEPTOR(void, mallinfo, __sanitizer_struct_mallinfo *sret) { in INTERCEPTOR() argument
104 internal_memset(sret, 0, sizeof(*sret)); in INTERCEPTOR()
105 dfsan_set_label(0, sret, sizeof(*sret)); in INTERCEPTOR()
/openbsd/gnu/llvm/compiler-rt/lib/hwasan/
H A Dhwasan_allocation_functions.cpp99 __sanitizer_struct_mallinfo sret; in __sanitizer_mallinfo() local
100 internal_memset(&sret, 0, sizeof(sret)); in __sanitizer_mallinfo()
101 return sret; in __sanitizer_mallinfo()
/openbsd/gnu/llvm/llvm/lib/Target/X86/
H A DREADME-X86-64.txt68 A better implementation would be to relax the LLVM IR rules for sret
69 arguments to allow a function with an sret argument to have a non-void
70 return type, and to have the front-end to set up the sret argument value
H A DX86CallingConv.td537 // For Swift Calling Conventions, pass sret in %rax.
682 // Do not pass the sret argument in RCX, the Win64 thiscall calling
971 // Pass sret arguments indirectly through stack.
/openbsd/gnu/llvm/compiler-rt/lib/msan/
H A Dmsan_interceptors.cpp249 INTERCEPTOR(void, mallinfo, __sanitizer_struct_mallinfo *sret) { in INTERCEPTOR() argument
253 sret = reinterpret_cast<__sanitizer_struct_mallinfo*>(r8); in INTERCEPTOR()
255 REAL(memset)(sret, 0, sizeof(*sret)); in INTERCEPTOR()
256 __msan_unpoison(sret, sizeof(*sret)); in INTERCEPTOR()
/openbsd/gnu/llvm/llvm/lib/Target/M68k/
H A DM68kCallingConv.td97 // TODO: Support for 'sret'
/openbsd/gnu/llvm/llvm/lib/Target/AArch64/
H A DAArch64CallingConvention.td45 // The "sret" attribute identifies indirect returns.
47 // The position of the "sret" attribute identifies instance/non-instance
49 // "sret" on argument 0 means non-instance methods.
50 // "sret" on argument 1 means instance methods.
/openbsd/sys/arch/hppa/include/
H A Dasm.h202 sret .reg %sr1 ; return value
/openbsd/gnu/llvm/llvm/utils/vim/syntax/
H A Dllvm.vim175 \ sret
/openbsd/gnu/llvm/llvm/lib/Target/Sparc/
H A DSparcCallingConv.td131 // returns that are too big to fit into the registers is passed as an sret
/openbsd/gnu/llvm/llvm/utils/
H A Dllvm.grm139 | sret
/openbsd/gnu/llvm/llvm/include/llvm/Target/
H A DTargetCallingConv.td90 /// CCIfSRet - If this argument is marked with the 'sret' attribute, apply
/openbsd/gnu/llvm/llvm/include/llvm/IR/
H A DAttributes.td253 def StructRet : TypeAttr<"sret", [ParamAttr]>;
/openbsd/gnu/llvm/llvm/docs/
H A DAssignmentTracking.md212 (e.g. sret, byval). We need to be able to handle those cases. See
H A DOpaquePointers.rst168 element type, such as byref, sret, inalloca and preallocated.
H A DBitCodeFormat.rst937 * bit 4: ``sret``
1035 * code 29: ``sret``
H A DAMDGPUUsage.rst13647 storing the result value. Clang terms this *structured return (sret)*.
13649 *TODO: correct the ``sret`` definition.*
13653 Is this definition correct? Or is ``sret`` only used if passing in registers, and
13844 - ``sret`` is after ``this`` pointer.
13853 - How is ``sret`` passed on the stack? In argument stack area? Can it overlay
/openbsd/gnu/gcc/gcc/config/pa/
H A Dmilli64.S121 sret: .reg sr1 /* return value */ label
/openbsd/gnu/usr.bin/gcc/gcc/config/pa/
H A Dmilli64.S102 sret: .reg sr1 /* return value */ label
/openbsd/sys/lib/libkern/arch/hppa/
H A Dmilli.S304 sret: .equ sr1 ; return value label
/openbsd/gnu/llvm/llvm/lib/Target/RISCV/
H A DRISCVInstrInfo.td799 def SRET : Priv<"sret", 0b0001000>, Sched<[]> {
/openbsd/gnu/llvm/llvm/lib/Target/
H A DREADME.txt2089 define void @testfunc(%struct.x* sret %agg.result) nounwind ssp {

12