Displaying 1 result from an estimated 1 matches for "goosey".
Did you mean:
goose
2017 Jan 03
4
RFC: Allow readnone and readonly functions to throw exceptions
...label %normal unwind label %unwind
normal:
ret i32 0
unwind:
%t = landingpad i32 cleanup
ret i32 %t
}
since it gets rid of a `resume` and thus a side effect (by
assumption).
# We're probably already there (but we need an audit)
All said and done, the situation is not as "loosey goosey" as I made
it sound like. mayHaveSideEffects() is defined as "mayWriteToMemory()
|| mayThrow()"; and this shows in e.g. EarlyCSE which will refuse to
DCE the call to @f in @g
declare void @f() readnone
define void @g() {
call void @f()
ret void
}
unless @f is also marked noun...