David Majnemer cc99e4e75c The absence of noreturn doesn't ensure mayReturn ... There are two separate issues: - LLVM doesn't consider infinite loops to be side effects: we happily hoist/sink above/below loops whose bounds are unknown. - The absence of the noreturn attribute is insufficient for us to know if a function will definitely return. Relying on noreturn in the middle-end for any property is an accident waiting to happen. llvm-svn: 273762		2016-06-25 00:55:12 +00:00
..
llvm	The absence of noreturn doesn't ensure mayReturn	2016-06-25 00:55:12 +00:00
llvm-c	Add support for string attributes in the C API.	2016-06-15 17:50:39 +00:00