similar to: [LLVMdev] Enable Detailed Output llvm-bcanalyzer

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:

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

Dear All, Does llvm-bcanalyzer still print the number of instructions in a bitcode file, or has that functionality been removed? -- John T.

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

When you do $ llvm-bcanalyzer hello.o | less you won't see anything, because bcanalyzer sends all of it's output to stderr. However, it get's it right when asked for help: $ llvm-bcanalyzer --help | less

Hello, llvm-bcanalyzer told me that the size of the BLOCKINFO_BLOCK of my file is "1.345017e+01" percent of the whole file. This is not very readable. The attached patch prints the percentage without scientific notation so we get something bit more readable: Block ID #0 (BLOCKINFO_BLOCK): Num Instances: 1 Total Size: 637b/79.62B/19W % of file: 13.450169 Num

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 Sep 29, 2009, at 9:44 AM, Timo Juhani Lindfors wrote: > 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. It looks like something similar got applied back in r82772 on 9/25. > > Btw,

Hi all, After updating llvm+clang to r174701 by issuing make -j8 happiness The build fails with: ... make[2]: Entering directory `/local/csaba/LLVM/build-release/tools/llvm-diff' llvm[2]: Compiling DiffConsumer.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts executable lli (without symbols) llvm[2]: Compiling CrashDebugger.cpp for Release+Asserts build

Chad, et al, In addition to Doug’s excellent technical update, I’ll note that we are starting to have some discussions on the DOE side with PGI about establishing a more formal review team made up of some key LLVM stakeholders to help smooth the way for a broader public rollout of the Flang code base and eventual integration. We’ll probably rely on Hal and others here to help us figure out who

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

> On May 26, 2016, at 1:57 PM, Neely, Rob via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Chad, et al, > > In addition to Doug’s excellent technical update, I’ll note that we are > starting to have some discussions on the DOE side with PGI about > establishing a more formal review team made up of some key LLVM > stakeholders to help smooth the way for a broader

No closed doors intended here. Just a recognition that for something like an initial review to be useful, we probably have to be a bit careful in how many people we can reasonably involve before it could get unwieldy, and trying to be respectful of people’s time if we can nail down 90% of issues with a smaller group before going broader. I think we’d be fine with opening up the WebEx presentations

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

On Fri, Apr 08, 2005 at 08:37:03AM -0700, Tanu Sharma wrote: > Regarding basic block size I wish to calculate both: > > - The number of bytecode bytes Use the llvm-bcanalyzer tool, it will tell you number of bytes per function and number of basic blocks. If you want number of bytes per basic block, check out what it does, and calculate basic blocks separately. > - The number of

Hi Chad - We have a functional Fortran compiler, with the PGI front-end bridged directly to LLVM, all of our Fortran runtime libraries integrated, and the Clang driver adapted for use with the Fortran compiler. We're working with a few users at DOE who are trying to compile big applications with a binary version of the compiler. Work is ongoing to migrate the source code into an LLVM-style

This process is certainly only open to a select group, so pragmatically it's closed. I can understand that it will certainly not be an easy process once it's public due to the amount of code and complexity. Maybe someone can comment on a specific issue - When we ported our Fortran front-end to target llvm, we found that Fortran ENTRY doesn't map very well to llvm ir. Can anyone who

Is there an announcements mailing list for samba? If not, could one please be created? I want to know when new releases are made, and when security holes are found, maybe even infrequent benchmark results, but unfortunately I don't have time to keep up with this list. My mailbox has been overflowing on a weekly basis, and it's got to stop, so I really need to decrease the volume coming

Reid, I finally figured out why my types were mismatching in my hand-decoded bytecode example when it worked fine in my actual code. It turns out that I was not leaving out the extension bits when I was hand decoding the VBRs. D'oh! Everything matches up now. Also figured out why the bcanalyzer is spitting out all those pointers to opaque. These types are forward references and they

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