search for: abortifbroken

Displaying 15 results from an estimated 15 matches for "abortifbroken".

2004 Apr 02
1
[LLVMdev] Verifier & abort()
...for (Module::giterator I = M.gbegin(), E = M.gend(); I != E; ++I) visitGlobalValue(*I); // If the module is broken, abort at this time. abortIfBroken(); return false; } The function visitGlobalValue will check one value, print out a message and set Broken=true. The abort doesn't happen until abortIfBroken() is called. Reid. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: app...
2009 Dec 23
5
[LLVMdev] Build Failure!
...+ 469 2 libSystem.B.dylib 0x00007fff814c7d5a _sigtramp + 26 3 libSystem.B.dylib 0x0000000100000001 _sigtramp + 2125693633 4 libSystem.B.dylib 0x00007fff81541119 raise + 25 5 libSystem.B.dylib 0x00007fff81561ddd abort + 90 6 opt 0x000000010abc99bf (anonymous namespace)::Verifier::abortIfBroken() + 239 7 opt 0x000000010abdbd6a (anonymous namespace)::Verifier::runOnFunction(llvm::Function&) + 140 8 opt 0x000000010ab93b13 llvm::FPPassManager::runOnFunction(llvm::Function&) + 387 9 opt 0x000000010ab8dd27 llvm::FPPassManager::runOnModule(ll...
2004 Apr 01
0
[LLVMdev] Verifier & abort()
On Thu, 1 Apr 2004, Reid Spencer wrote: > On Thu, 2004-04-01 at 18:04, Misha Brukman wrote: > > > Perhaps another solution would be to throw an exception with the error > > message? > > Perhaps, but that would violate the programming contract already in > place. Right now LLVM and its users expect failed verifications to cause > an abort(). I wouldn't want to
2005 Jun 20
2
[LLVMdev] 'make check' failed with: ... PHI node entries do not match predecessors! ...
...l [ true, %no_exit ], [ %tmp.7, %shortcirc_next ] ; <bool> [#uses=1] label %no_exit label <badref> Broken module found, compilation aborted! gccas((anonymous namespace)::PrintStackTrace()+0x1f)[0x82b8c3f] /lib/tls/libc.so.6(abort+0x1d2)[0x363302] gccas((anonymous namespace)::Verifier::abortIfBroken()+0x196)[0x8235fb6] gccas(llvm::PassManagerTraits<llvm::Function>::runOnFunction(llvm::Function&)+0x17)[0x82201d7] Output/2005-06-15-ExpandGotoInternalProblem.c.out.script: line 1: 5013 Done PATH="/home/hb/projects/build/FC1/llvm-1-1/Debug/bin:/home/hb/projects...
2009 Dec 23
0
[LLVMdev] Build Failure!
...B.dylib 0x00007fff814c7d5a _sigtramp + 26 > 3 libSystem.B.dylib 0x0000000100000001 _sigtramp + 2125693633 > 4 libSystem.B.dylib 0x00007fff81541119 raise + 25 > 5 libSystem.B.dylib 0x00007fff81561ddd abort + 90 > 6 opt 0x000000010abc99bf (anonymous namespace)::Verifier::abortIfBroken() + 239 > 7 opt 0x000000010abdbd6a (anonymous namespace)::Verifier::runOnFunction(llvm::Function&) + 140 > 8 opt 0x000000010ab93b13 llvm::FPPassManager::runOnFunction(llvm::Function&) + 387 > 9 opt 0x000000010ab8dd27 llvm::FPPassManager:...
2004 Apr 01
4
[LLVMdev] Verifier & abort()
On Thu, 2004-04-01 at 18:04, Misha Brukman wrote: > Perhaps another solution would be to throw an exception with the error > message? Perhaps, but that would violate the programming contract already in place. Right now LLVM and its users expect failed verifications to cause an abort(). I wouldn't want to unleash on LLVM the new semantics of now handling exceptions in every place the
2005 Jun 20
0
[LLVMdev] 'make check' failed with: ... PHI node entries do not match predecessors! ...
...ortcirc_next > ] ; <bool> [#uses=1] > label %no_exit > label <badref> > Broken module found, compilation aborted! > gccas((anonymous namespace)::PrintStackTrace()+0x1f)[0x82b8c3f] > /lib/tls/libc.so.6(abort+0x1d2)[0x363302] > gccas((anonymous namespace)::Verifier::abortIfBroken()+0x196)[0x8235fb6] > gccas(llvm::PassManagerTraits<llvm::Function>::runOnFunction(llvm::Function&)+0x17)[0x82201d7] > Output/2005-06-15-ExpandGotoInternalProblem.c.out.script: line 1: 5013 Done > > PATH="/home/hb/projects/build/FC1/llvm-1-1/Debug/b...
2005 Jun 20
1
[LLVMdev] 'make check' failed with: ... PHI node entries donot match predece
...ol> [#uses=1] > > label %no_exit > > label <badref> > > Broken module found, compilation aborted! > > gccas((anonymous namespace)::PrintStackTrace()+0x1f)[0x82b8c3f] > > /lib/tls/libc.so.6(abort+0x1d2)[0x363302] > > gccas((anonymous namespace)::Verifier::abortIfBroken()+0x196)[0x8235fb6] > > >gccas(llvm::PassManagerTraits<llvm::Function>::runOnFunction(llvm::Function&)+0x17)[0x82201d7] > > Output/2005-06-15-ExpandGotoInternalProblem.c.out.script: line 1: 5013 >Done > > > > >PATH="/home/hb/projects/build/FC1/llv...
2011 Oct 11
2
[LLVMdev] interprocedural static backwards slicing
...0x0000000106fdea49 _ZL13SignalHandleri + 553 2 libsystem_c.dylib 0x00007fff92d42cfa _sigtramp + 26 3 opt 0x0000000106f02ff1 llvm::UpgradeIntrinsicFunction(llvm::Function*, llvm::Function*&) + 3633 4 opt 0x0000000106f97fc7 (anonymous namespace)::Verifier::abortIfBroken() + 311 5 opt 0x0000000106fa5138 (anonymous namespace)::Verifier::runOnFunction(llvm::Function&) + 2304 6 opt 0x0000000106f80b7c llvm::FPPassManager::runOnFunction(llvm::Function&) + 392 7 opt 0x0000000106f7bc7b llvm::FPPassManager::runOnModule(l...
2011 Oct 11
0
[LLVMdev] interprocedural static backwards slicing
...a49 _ZL13SignalHandleri + 553 > 2 libsystem_c.dylib 0x00007fff92d42cfa _sigtramp + 26 > 3 opt 0x0000000106f02ff1 > llvm::UpgradeIntrinsicFunction(llvm::Function*, llvm::Function*&) + 3633 > 4 opt 0x0000000106f97fc7 (anonymous > namespace)::Verifier::abortIfBroken() + 311 > 5 opt 0x0000000106fa5138 (anonymous > namespace)::Verifier::runOnFunction(llvm::Function&) + 2304 > 6 opt 0x0000000106f80b7c > llvm::FPPassManager::runOnFunction(llvm::Function&) + 392 > 7 opt 0x0000000106f7bc7b > llvm...
2005 Jun 13
0
[LLVMdev] problem compiling the cfrontend on Linux/PPC
Cyrille Mescam wrote: > On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote: > >>Cyrille Mescam wrote: >> [snip] > > In fact, i am using the CFE build procedures. I am on instructions 5. > > cyrille > Okay, I took a closer look at your output. I was correct in that gccas is attempting to assemble a native PPC assembly language file. However,
2005 Jun 13
2
[LLVMdev] problem compiling the cfrontend on Linux/PPC
On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote: > Cyrille Mescam wrote: > >Hi, > > > > > >When compiling the cfrontend for Linux/PPC architecture on a powermac > >G5, i got > >the following error : > > I hate to ask a silly question, but are you using "make bootstrap" to > build the cfrontend? Your output looks like gccas
2005 Jun 13
2
[LLVMdev] problem compiling the cfrontend on Linux/PPC
...le found, compilation aborted! gccas((anonymous namespace)::PrintStackTrace()+0x24)[0x1066da30] gccas((anonymous namespace)::SignalHandler(int)+0x100)[0x1066dcdc] [0x7fffc1a8] gccas(__libc_csu_init+0x0)[0x1066ed60] /lib/libc.so.6(abort+0x1b8)[0xfcda018] gccas((anonymous namespace)::Verifier::abortIfBroken()+0x10c)[0x10569e18] gccas((anonymous namespace)::Verifier::runOnFunction(llvm::Function&)+0x7c)[0x10569f9c] gccas(llvm::PassManagerTraits<llvm::Function>::runPass(llvm::FunctionPass*, llvm::Function*)+0x3c)[0x105428b4] gccas(llvm::PassManagerT<llvm::Function>::runOnUnit(llvm::...
2011 Oct 10
0
[LLVMdev] interprocedural static backwards slicing
On 10/9/11 12:12 AM, Jinwook Shin wrote: > Thanks John. I appreciate your help and I look forward to obtaining the code. > > A proper LLVM sub-project: No rush on this and please take your time. Thanks. Okay, I've created a new LLVM sub-project called Giri(*). It currently contains only the static backwards slicing pass. I'll add the dynamic slicing code to the project later.
2011 Oct 09
2
[LLVMdev] interprocedural static backwards slicing
Thanks John. I appreciate your help and I look forward to obtaining the code. A proper LLVM sub-project: No rush on this and please take your time. Thanks. - Jin -----Original Message----- From: Criswell, John T [mailto:criswell at illinois.edu] Sent: Saturday, October 08, 2011 11:58 AM To: Jinwook Shin; llvmdev at cs.uiuc.edu Subject: RE: interprocedural static backwards slicing Dear Jin,