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

Hello all, Does anyone know how to make llvm-bcanalyzer produce detailed output i.e. provides additional information on a per-function basis. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111105/8e7fe152/attachment.html>

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>

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

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

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

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

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,

I used this service several months ago and was very pleased with the response. I have a dataframe with several thousand lines and to each line I need to apply a series of "if else" statements. For each row I need either a value or a blank/NA. Below is the series of if else statements I have been trying without success to integrate into a function such as "apply". if

Hello. I am trying to copy an entire directory structure from a Unix box to an NT share using a command like this: tar -c -h -O /usr/local/sh | smbclient //ntstldls01/rs8724$ -Tx - -D chico -U myuser%mypasswd The problem is it chokes when it hits a file with 2 links (hard links - not sym links). I am using "-h" with tar to try to force it to copy the file rather than the link, but

https://bugzilla.samba.org/show_bug.cgi?id=11189 Bug ID: 11189 Summary: dry run gives incomplete log Product: rsync Version: 3.0.9 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: riquet at

> On Oct 13, 2014, at 6:59 PM, Sean Silva <chisophugis at gmail.com> wrote: > > Stupid question, but when I was working on LTO last Summer the primary culprit for excessive memory use was due to us not being smart when linking the IR together (Espindola would know more details). Do we still have that problem? For starters, how does the memory usage of just llvm-link compare to the

In r219010, I merged integer and string fields into a single header field. By reducing the number of metadata operands used in debug info, this saved 2.2GB on an `llvm-lto` bootstrap. I've done some profiling of DW_TAGs to see what parts of PR17891 and PR17892 to tackle next, and I've concluded that they will be insufficient. Instead, I'd like to implement a more aggressive plan,