[MCJIT] Make stub_addr functionality in RuntimeDyldChecker work in release mode.
authorLang Hames <lhames@gmail.com>
Tue, 22 Jul 2014 23:50:51 +0000 (23:50 +0000)
committerLang Hames <lhames@gmail.com>
Tue, 22 Jul 2014 23:50:51 +0000 (23:50 +0000)
There's no reason to restrict this particular piece of RuntimeDyldChecker
functionality to +Asserts builds.

This should fix failures in MachO_x86-64_PIC_relocations.s on release bots.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@213708 91177308-0d34-0410-b5e6-96231b3b80d8

lib/ExecutionEngine/RuntimeDyld/RuntimeDyld.cpp

index 7434c2a06666f35915344d01fe266aec78426d1f..810fbfff2f5d8519cbd716f0aec9d32459ace5fa 100644 (file)
@@ -206,12 +206,10 @@ ObjectImage *RuntimeDyldImpl::loadObject(ObjectImage *InputObject) {
       I = processRelocationRef(SectionID, I, *Obj, LocalSections, LocalSymbols,
                                Stubs);
 
       I = processRelocationRef(SectionID, I, *Obj, LocalSections, LocalSymbols,
                                Stubs);
 
-#ifndef NDEBUG
     // If there is an attached checker, notify it about the stubs for this
     // section so that they can be verified.
     if (Checker)
       Checker->registerStubMap(Obj->getImageName(), SectionID, Stubs);
     // If there is an attached checker, notify it about the stubs for this
     // section so that they can be verified.
     if (Checker)
       Checker->registerStubMap(Obj->getImageName(), SectionID, Stubs);
-#endif
   }
 
   // Give the subclasses a chance to tie-up any loose ends.
   }
 
   // Give the subclasses a chance to tie-up any loose ends.