Fix a 64-bit problem, passing (int)0 through ... instead of (void*)0
authorChris Lattner <sabre@nondot.org>
Thu, 9 Jun 2005 03:32:54 +0000 (03:32 +0000)
committerChris Lattner <sabre@nondot.org>
Thu, 9 Jun 2005 03:32:54 +0000 (03:32 +0000)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@22206 91177308-0d34-0410-b5e6-96231b3b80d8

lib/Transforms/Utils/LowerInvoke.cpp

index b0c807f958a60c20d84cf3b6151b37cb4bbfd8b6..fe22b4be847985ca30cffa610d9ca45df3d44163 100644 (file)
@@ -116,14 +116,14 @@ bool LowerInvoke::doInitialization(Module &M) {
                                       Constant::getNullValue(PtrJBList),
                                       "llvm.sjljeh.jblist", &M);
     SetJmpFn = M.getOrInsertFunction("llvm.setjmp", Type::IntTy,
-                                     PointerType::get(JmpBufTy), 0);
+                                     PointerType::get(JmpBufTy), NULL);
     LongJmpFn = M.getOrInsertFunction("llvm.longjmp", Type::VoidTy,
                                       PointerType::get(JmpBufTy),
-                                      Type::IntTy, 0);
+                                      Type::IntTy, NULL);
   }
 
   // We need the 'write' and 'abort' functions for both models.
-  AbortFn = M.getOrInsertFunction("abort", Type::VoidTy, 0);
+  AbortFn = M.getOrInsertFunction("abort", Type::VoidTy, NULL);
 
   // Unfortunately, 'write' can end up being prototyped in several different
   // ways.  If the user defines a three (or more) operand function named 'write'
@@ -140,7 +140,7 @@ bool LowerInvoke::doInitialization(Module &M) {
       WriteFn = 0;
   } else {
     WriteFn = M.getOrInsertFunction("write", Type::VoidTy, Type::IntTy,
-                                    VoidPtrTy, Type::IntTy, 0);
+                                    VoidPtrTy, Type::IntTy, NULL);
   }
   return true;
 }