bcm5719-llvm - Project Ortega BCM5719 LLVM

	Commit message (Collapse)	Author	Age	Files	Lines
*	Improve a -Wunguarded-availability note	Erik Pilkington	2019-01-14	1	-4/+4
\| \| \| \| \| \| \| \| \| \| \|	Mention the deployment target, and don't say "partial" which doesn't really mean anything to users. rdar://problem/33601513 Differential revision: https://reviews.llvm.org/D56523 llvm-svn: 351108
*	[Sema] Improve some -Wunguarded-availability diagnostics	Erik Pilkington	2017-08-14	1	-4/+4
\| \| \| \| \| \| \|	rdar://33543523 Differential revision: https://reviews.llvm.org/D36200 llvm-svn: 310874
*	[Sema] Don't allow -Wunguarded-availability to be silenced with redecls	Erik Pilkington	2017-07-05	1	-4/+4
\| \| \| \| \| \|	Differential revision: https://reviews.llvm.org/D33816 llvm-svn: 307175
*	[Sema] Add -Wunguarded-availability-new	Alex Lorenz	2017-06-22	1	-0/+160
	The new compiler warning -Wunguarded-availability-new is a subset of -Wunguarded-availability. It is on by default. It only warns about uses of APIs that have been introduced in macOS >= 10.13, iOS >= 11, watchOS >= 4 and tvOS >= 11. We decided to use this kind of solution as we didn't want to turn on -Wunguarded-availability by default, because we didn't want our users to get warnings about uses of old APIs in their existing projects. rdar://31054725 Differential Revision: https://reviews.llvm.org/D34264 llvm-svn: 306033