llvm-project

Commit Graph

Author	SHA1	Message	Date
David Blaikie	a953f2825b	Update Clang tests to handle explicitly typed load changes in LLVM. llvm-svn: 230795	2015-02-27 21:19:58 +00:00
Stephen Lin	4362261b00	CHECK-LABEL-ify some code gen tests to improve diagnostic experience when tests fail. llvm-svn: 188447	2013-08-15 06:47:53 +00:00
Douglas Gregor	1c15cd6aaa	CodeGenFunction::CurFuncDecl can be NULL; fix crash introduced in r175386. llvm-svn: 175448	2013-02-18 15:59:24 +00:00
Dmitri Gribenko	dfe49e8c31	Test ivar-invariant.m: use a more idiomatic RUN line and tighten the test by matching the function name first llvm-svn: 175395	2013-02-17 14:59:41 +00:00
Saleem Abdulrasool	7a786f8c7a	[clang] fix test execution command Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org> llvm-svn: 175387	2013-02-17 04:13:35 +00:00
Saleem Abdulrasool	5f25bc30d1	[CodeGen] tighten objc ivar invariant.load attribution An ivar ofset cannot be marked as invariant load in all cases. The ivar offset is a lazily initialised constant, which is dependent on an objc_msgSend invocation to perform a fixup of the offset. If the load is being performed on a method implemented by the class then this load can safely be marked as an inviarant because a message must have been passed to the class at some point, forcing the ivar offset to be resolved. An additional heuristic that can be used to identify an invariant load would be if the ivar offset base is a parameter to an objc method. However, without the parameters available at hand, this is currently not possible. Reviewed-by: John McCall <rjmccall@apple.com> Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org> llvm-svn: 175386	2013-02-17 04:03:34 +00:00

6 Commits