search for: cgsccpassmgr

....bc -o tmp.bc2 D:\ >opt -stats temp.bc -o tmp.bc2 -O3 ===-------------------------------------------------------------------------=== ... Statistics Collected ... ===-------------------------------------------------------------------------=== 1 cgscc-passmgr - Maximum CGSCCPassMgr iterations on one SCC 3 reassociate - Number of insts reassociated From: Rafael Parizi [mailto:parizi.computacao at gmail.com] Sent: Tuesday, June 12, 2012 1:27 PM To: Villmow, Micah Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] output -stats to file.txt Yes, I've tried and it did not...

...------------------------------------------------------------=== > **** > > ... Statistics Collected ...**** > > > ===-------------------------------------------------------------------------=== > **** > > ** ** > > 1 cgscc-passmgr - Maximum CGSCCPassMgr iterations on one SCC**** > > 3 reassociate - Number of insts reassociated**** > > ** ** > > ** ** > > *From:* Rafael Parizi [mailto:parizi.computacao at gmail.com] > *Sent:* Tuesday, June 12, 2012 1:27 PM > *To:* Villmow, Micah > *Cc:* llvmdev at cs.uiuc.edu >...

Yes, I've tried and it did not work On Tue, Jun 12, 2012 at 4:03 PM, Villmow, Micah <Micah.Villmow at amd.com>wrote: > Have you tried "opt -stats bitecode.bc > test.txt"?**** > > ** ** > > *From:* llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] *On > Behalf Of *Rafael Parizi > *Sent:* Tuesday, June 12, 2012 11:36 AM > *To:*

...-argpromotion pass. However, it fails to do anything to the resulting llvm file. List of commands: clang add.c -c -o add.bc clang add.c -S -o add.ll opt -argpromotion -stats add.bc -o add_a.bc llvm-dis < add_a.bc > add_a.ll Also, when I try to print the stats I get a message "Maximum CGSCCPassMgr iterations on one SCC" Can anyone please let me know what I am missing here? Thanks for all the help. Regards Arvind

Right, this gets into the whole error-handling philosophy of LLVM, or lack thereof. The idea is that so long as your frontend generating IR gives correct IR and is well-behaved, LLVM will not assert, abort, or crash. Once you've successfully debugged your frontend, you should never see this kind of error from LLVM and need to recover from it. In practice, this is true enough that it is

I'm trying to figure out the best way to handle signals raised during the execution of LLVM's optimization passes or the JIT'ing of code prior to running it. In particular, LLVM throws unix signals instead of C++ exceptions while the header ErrorHandling.h contains the following warning (the last paragraph in particular): /// llvm_instal_error_handler - Installs a new error handler