Displaying 1 result from an estimated 1 matches for "scc_bottom_vs_top_fn_top".
2018 Aug 23
2
[RFC] "Properly" Derive Function/Argument/Parameter Attributes
...i32* @external_sink_ret2_nrw(i32* %n0, i32* %r0, i32* %w0)
%call1 = call i32* @external_ret2_nrw(i32* %n0, i32* %r0, i32* %w0)
ret i32* %call1
}
-------------- next part --------------
; RUN: opt -S -functionattrs -enable-nonnull-arg-prop %s | FileCheck %s
; In the following SCC, one function (scc_bottom_vs_top_fn_top) cannot be
; marked nonnull. We should still mark the others as they will always return
; nonnull pointers. However, this only works if we initialize our abstract
; state with bottom (not top), thus optimistically assume nonnull until proven
; otherwise.
declare nonnull i8* @ret_nonnull()
; CHECK...