From 6fb117d939574537f2528e435b6c610babbb9ae1 Mon Sep 17 00:00:00 2001 From: Jim Grosbach Date: Fri, 14 Mar 2014 22:41:58 +0000 Subject: MC: don't create a backtrace for diagnostics. For better or worse, this is currently the normal error reporting path when dealing with backend errors from inline assembly. It's not just internal compiler issues that come through here, so we shouldn't be creating a backtrace on this path. rdar://16329947 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@203979 91177308-0d34-0410-b5e6-96231b3b80d8 --- lib/MC/MCContext.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lib/MC/MCContext.cpp') diff --git a/lib/MC/MCContext.cpp b/lib/MC/MCContext.cpp index 198ae45cdf..ede3b3cd23 100644 --- a/lib/MC/MCContext.cpp +++ b/lib/MC/MCContext.cpp @@ -353,7 +353,7 @@ void MCContext::FatalError(SMLoc Loc, const Twine &Msg) { // If we have a source manager and a location, use it. Otherwise just // use the generic report_fatal_error(). if (!SrcMgr || Loc == SMLoc()) - report_fatal_error(Msg); + report_fatal_error(Msg, false); // Use the source manager to print the message. SrcMgr->PrintMessage(Loc, SourceMgr::DK_Error, Msg); -- cgit v1.2.3