summaryrefslogtreecommitdiffstats
path: root/clang/test/CodeGenObjCXX/property-object-reference.mm
Commit message (Collapse)AuthorAgeFilesLines
* Update Clang tests to handle explicitly typed load changes in LLVM.David Blaikie2015-02-271-2/+2
| | | | llvm-svn: 230795
* Don't manually insert L prefixes.Rafael Espindola2014-11-061-2/+2
| | | | | | Simply marking the symbol private conveys the desire to hide them to LLVM. llvm-svn: 221451
* Restructure how the driver communicates information about theJohn McCall2012-06-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | target Objective-C runtime down to the frontend: break this down into a single target runtime kind and version, and compute all the relevant information from that. This makes it relatively painless to add support for new runtimes to the compiler. Make the new -cc1 flag, -fobjc-runtime=blah-x.y.z, available at the driver level as a better and more general alternative to -fgnu-runtime and -fnext-runtime. This new concept of an Objective-C runtime also encompasses what we were previously separating out as the "Objective-C ABI", so fragile vs. non-fragile runtimes are now really modelled as different kinds of runtime, paving the way for better overall differentiation. As a sort of special case, continue to accept the -cc1 flag -fobjc-runtime-has-weak, as a sop to PLCompatibilityWeak. I won't go so far as to say "no functionality change", even ignoring the new driver flag, but subtle changes in driver semantics are almost certainly not intended. llvm-svn: 158793
* obj-c++: allow the getter/setter to return/take parametersFariborz Jahanian2011-10-151-0/+12
| | | | | | by reference. // rdar://10188258 llvm-svn: 142075
* objc++: Accessing explicit property of reference type need Fariborz Jahanian2011-10-031-0/+23
not bind to a temporary. Fixes //rdar://10188258 llvm-svn: 141009
OpenPOWER on IntegriCloud