similar to: [LLVMdev] Instruction Count in llvm-bcanalyzer

On Mar 30, 2009, at 12:08 PM, John Criswell wrote: > Dear All, > > Does llvm-bcanalyzer still print the number of instructions in a > bitcode > file, or has that functionality been removed? Try the "opt -instcount -stats" option, -Chris

Hello, I'm trying to print the instruction count of a bytecode file using the 2.4 release of LLVM. I found llvm-2.4/lib/Analysis/Instcount.cpp but I'm not sure what to do with it. I also looked at llvm-bcanalyzer. The documentation says this command is supposed to print the instruction count in the summary, but it doesn't seem to be doing so. Does anyone know what I should be

Patrick Simmons wrote: > Hello, > > I'm trying to print the instruction count of a bytecode file using the > 2.4 release of LLVM. I found llvm-2.4/lib/Analysis/Instcount.cpp but > I'm not sure what to do with it. I also looked at llvm-bcanalyzer. The > documentation says this command is supposed to print the instruction > count in the summary, but it doesn't

Chad, Yes it helps, thanks. I have started hacking bitcode-analyzer. ---ajonwa ----- Original Message ----- From: Chad Rosier Sent: 11/05/11 09:07 PM To: ajonwa ajonwa Subject: Re: [LLVMdev] Enable Detailed Output llvm-bcanalyzer ajonwa, It will provide some of the information you're seeking, but not all. Here's a partial dump from one of the bitcode test cases:

On Wed, Jun 7, 2017 at 8:58 AM, Charles Saternos <charles.saternos at gmail.com > wrote: > Alright, now it outputs YAML in the following format: > > --- > NamedGlobalValueMap: > X: > - Kind: GlobalVar > Linkage: ExternalLinkage > NotEligibleToImport: false > Live: false > a: > - Kind:

2017-06-06 13:38 GMT-07:00 David Blaikie <dblaikie at gmail.com>: > > > On Tue, Jun 6, 2017 at 1:26 PM Mehdi AMINI <joker.eph at gmail.com> wrote: > >> 2017-06-05 14:27 GMT-07:00 David Blaikie via llvm-dev < >> llvm-dev at lists.llvm.org>: >> >>> I know there's been a bunch of discussion here already, but I was >>> wondering if

Great! For the hotness, try creating a small test case with a very hot loop that iterates many times. Let me know if you are still having trouble. While the llvm-dis serialization is being discussed, I suppose at the very least this can go in with the rest of the existing YAML summary dumping and get emitted from llvm-lto2 using the patch Peter attached. Peter - do you want to add that to

Hi, Andreas Neustifter <astifter-llvm at gmx.at> writes: > Maybe you can use the already available "include/llvm/Support/Format.h"? Thanks, that simplifies the patch a lot. See the attached patch. Btw, llvm-bcanalyzer.cpp seems to also use fprintf -- does mixing it with errs() cause problems and should it be converted to use format()? best regards, Timo Lindfors

Hi Teresa, Thanks for the detailed reply! > How are you creating your bitcode files? I create the bitcode with `-flto=thin -c` and sure it has a GLOBALVAL_SUMMARY_BLOCK. And there’s no RegularLTO partition only ThinLTO bicode. > Where is it aborting in the backend? It aborts at ` report_fatal_error("Failed to setup codegen")` in of codegen() of LTOBackend.cpp. And before that in

Hello, I'm considering LLVM for a project, and I wanted to take a look at its bytecode representation/instruction set. So I decided to try to compile the /bin/ls command as bytecode (no particular reason to use ls) and look at it. So I got GNU coreutils from http://ftp.gnu.org/gnu/coreutils/coreutils-5.0.tar.gz, built it to make sure it works, then replaced gcc, ld, ar and ranlib with

Hi, I'd like a simple and fast way to collect the number of times each Instruction was executed in a given run of the application. As far as I can tell, there are a number of approaches I can take: - Use PIN. This would require using DWARF debug info and Instruction debug info to attempt to map instructions in the binary to instructions in the bitcode; not 100% sure how accurate this will

Hello, I have implemented a pass to count total number of instructions in LLVM 8.0. Its source code is attached here. The pass runs fine with LLVM 4.0. But with LLVM 8.0 following error is shown; $ $LLVMopt_BIN/opt -load $LLVM_SO/LLVMStatic-Info.so -one output-simple.bc WARNING: You're attempting to print out a bitcode file. This is inadvisable as it may cause display problems. If you REALLY

Hi, As part of PR27551 I want to add a string table to the bitcode format to allow global value and comdat names to be shared with the proposed symbol table (and, as side effects, allow comdat names to be shared with value names, make bitcode files more compressible and make bitcode easier to parse). The format of the string table would be a top-level block containing a blob containing

On Tue, Nov 6, 2012 at 2:19 PM, Marshall Clow <mclow.lists at gmail.com> wrote: > Binutils and LLVM > > As part of "owning our own toolchain", various people have expressed an interest and have been working on creating various tools that duplicate the functionality of tools available on other systems. > > As a start, I'd like to summarize the current status, and

Reid Spencer <rspencer <at> reidspencer.com> writes: > Hi Joshua, Hi, thanks for the reply. > On Mon, 2007-09-03 at 21:34 +0000, Joshua Haberman wrote: > > I also have a few questions about the format: > > > > - it appears that the only magic number in the file is > > application-specific. This seems unfortunate, because it means that > >

Hi Joshua, On Mon, 2007-09-03 at 21:34 +0000, Joshua Haberman wrote: > Greetings, > > I am working on a project (unrelated to LLVM) that needed a > bytecode-like format. I found Bitcode and it seems to fit the bill > really nicely. > > I am writing an independent implementation of Bitcode in C (I really > want to keep my runtime pure C). In the process of doing this,

On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > Hi, > > As part of PR27551 I want to add a string table to the bitcode format to > allow global value and comdat names to be shared with the proposed symbol > table (and, as side effects, allow comdat

conversion of llvm-bcanalyzer.cpp compiles, but not runtime tested Cheers, Gabor -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: llvm-bcanalyzer.cpp.diff URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070704/b12afa40/attachment.ksh>

On Tue, Apr 4, 2017 at 1:25 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Apr 4, 2017, at 12:12 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: >> >> Hi,

On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > Hi, > > As part of PR27551 I want to add a string table to the bitcode format to > allow global value and comdat names to be shared with the proposed symbol > table (and, as side effects, allow comdat