Displaying 2 results from an estimated 2 matches for "in_reg".
Did you mean:
il_reg
2015 Sep 28
4
varargs, the x86, and clang
...r.ph
%gp_offset = phi i32 [ %gp_offset.pre, %for.body.lr.ph ], [ %gp_offset10,
%vaarg.end ]
%sum.09 = phi i32 [ 0, %for.body.lr.ph ], [ %add, %vaarg.end ]
%i.08 = phi i32 [ 0, %for.body.lr.ph ], [ %inc, %vaarg.end ]
%fits_in_gp = icmp ult i32 %gp_offset, 41
br i1 %fits_in_gp, label %vaarg.in_reg, label %vaarg.in_mem
vaarg.in_reg: ; preds = %for.body
%reg_save_area = load i8** %0, align 16
%1 = sext i32 %gp_offset to i64
%2 = getelementptr i8* %reg_save_area, i64 %1
%3 = add i32 %gp_offset, 8
store i32 %3, i32* %gp_offset_p, align 16
br label...
2020 Nov 11
1
[RFC] A value-tracking LiveDebugValues implementation
...a little puzzle about the " drop the DBG_VALUE ", maybe I didn't get your key point,
> So I write a phi case, it like
> ___________________________________________________
> vaarg.end: ; preds = %vaarg.in_mem, %vaarg.in_reg
> %5 = phi i32 [ %4, %vaarg.in_reg ], [ %l5, %vaarg.in_mem ], !dbg !50
> %6 = add nsw i32 %gp_offset, %vaarg.l, !dbg !41
> call void @llvm.dbg.value(metadata i32 %5, metadata !28, metadata !DIExpression()), !dbg !50
> ret i32 %6, !dbg !52
> ___________________________________...