Displaying 1 result from an estimated 1 matches for "error_return_trac".
Did you mean:
error_return_trace
2018 Mar 29
0
workaround for CoroSplit not spilling alloca?
My frontend is emitting an array (here called
%error_return_trace_addresses). You can see we take the address of the
first element and store it
; Function Attrs: nobuiltin noinline nounwind optnone
define internal fastcc i8* @failing(%StackTrace* nonnull, %Allocator*,
i16*) unnamed_addr #3 !dbg !273 {
Entry:
%error_return_trace_addresses = alloca [1 x i64], a...