Use failCompilation instead of explicit throw

Update the code to use TR::Compilation::failCompilation instead of
explicitly throwing an exception since the failCompilation method
provides a debugging message that helps determine where an exception was
thrown from.

Signed-off-by: Irwin D'Souza <dsouzai@ca.ibm.com>

Author: Irwin D'Souza

compiler/compile/OMRCompilation.cpp

@@ -1162,10 +1162,10 @@ int32_t OMR::Compilation::compile()
    // If that happened we want to fail the compilation at this point.
    //
    if (_methodSymbol->unimplementedOpcode())
-      throw TR::UnimplementedOpCode();
+      self()->failCompilation<TR::UnimplementedOpCode>("Unimplemented Op Code");
 
    if (!_ilGenSuccess)
-      throw TR::ILGenFailure();
+      self()->failCompilation<TR::ILGenFailure>("IL Gen Failure");
 
 #ifdef J9_PROJECT_SPECIFIC
    if (self()->getOption(TR_TraceCG))

compiler/infra/Assert.cpp

@@ -93,7 +93,7 @@ static void assumeDontCallMeDirectlyImpl( const char * file, int32_t line, const
    // Fatal assertions fire always, however, non fatal assertions
    // can be disabled via TR_SoftFailOnAssume.
    if (comp && comp->getOption(TR_SoftFailOnAssume) && !fatal)
-      throw TR::AssertionFailure();
+      comp->failCompilation<TR::AssertionFailure>("Assertion Failure");
 
    // Default is to always print to screen
    bool printOnscreen = true;