bcm5719-llvm - Project Ortega BCM5719 LLVM

	Commit message (Collapse)	Author	Age	Files	Lines
*	Don't diagnoes a mismatch between implicit and explicit exception	Richard Smith	2016-08-31	1	-0/+2
\| \| \| \| \| \| \|	specifications under -fno-exceptions, just as we don't diagnose other exception specification mismatch errors. llvm-svn: 280289
*	Prior to adding the new "expected-no-diagnostics" directive to ↵	Andy Gibbs	2012-10-19	1	-0/+1
\| \| \| \| \| \|	VerifyDiagnosticConsumer, make the necessary adjustment to 580 test-cases which will henceforth require this new directive. llvm-svn: 166280
*	When a declaration of a function is missing an exception specification	Douglas Gregor	2010-03-24	1	-0/+13
	that was present in a prior declaration, emit a warning rather than a hard error (which we did before, and still do with mismatched exception specifications). Moreover, provide a fix-it hint with the throw() clause that should be added, e.g., t.C:10:7: warning: 'operator new' is missing exception specification 'throw(std::bad_alloc)' void *operator new(unsigned long sz) ^ throw(std::bad_alloc) As part of this, disable the warning when we're missing an exception specification on operator new, operator new[], operator delete, or operator delete[] when exceptions are turned off (-fno-exceptions). Fixes PR5957. llvm-svn: 99388