similar to: [LLVMdev] bitcode / bytecode

Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] bitcode / bytecode"

2010 Sep 29
1
[LLVMdev] Fwd: bitcode / bytecode
Anyone, can you say what was the reason to rename bytecode? I am still interesting in 2010/9/29 Duncan Sands <baldrick at free.fr> Hi Ariel, > As long as I know English the word "bit" is a "small pice", . Why in set of > documentation ir is "bytecode", in other set or llvm source is "bitecode"? > What is the right? Different people call the
2010 Sep 29
0
[LLVMdev] Fwd: bitcode / bytecode
Chris rewrote the original LLVM bytecode into it's present bitcode form. The newer code is much smaller than the previous form. That would be my guess for why he chose to call it bitcode. Of course, he can say for himself. :-) -bw On Sep 29, 2010, at 5:15 AM, Ariel Feinerman wrote: > Anyone, > > can you say what was the reason to rename bytecode? I am still interesting in >
2010 Sep 29
0
[LLVMdev] bitcode / bytecode
Hi Ariel, > can you say what was the reason to rename bytecode? I am still interesting in you forgot to send this to the mailing list, so I have (probably someone there knows better than I). I think the reason is that bitcode is bit-packed, i.e. you can have multiple pieces of information stored in one byte, so byte code was a misnomer. Ciao, Duncan. > > 2010/9/29 Duncan Sands
2012 Jun 12
2
[LLVMdev] output -stats to file.txt
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:*
2012 Jun 12
0
[LLVMdev] output -stats to file.txt
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: llvmdev at cs.uiuc.edu Subject: [LLVMdev] output -stats to file.txt Hi! I'm estimating the number of basic blocks of the a program using "opt -stats bitecode.bc" I would
2012 Jun 12
2
[LLVMdev] output -stats to file.txt
Hi! I'm estimating the number of basic blocks of the a program using "opt -stats bitecode.bc" I would like to save the output of the -stats opt into a file .txt. How can I do this? -- *Rafael Parizi* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120612/cc314c37/attachment.html>
2012 Jun 12
0
[LLVMdev] output -stats to file.txt
Add an optimization level and you get information. D:\ >opt -stats temp.bc -o tmp.bc2 D:\ >opt -stats temp.bc -o tmp.bc2 -O3 ===-------------------------------------------------------------------------=== ... Statistics Collected ... ===-------------------------------------------------------------------------=== 1 cgscc-passmgr - Maximum CGSCCPassMgr iterations on
2012 Jun 12
1
[LLVMdev] output -stats to file.txt
I already did. What I need is to have this output in a txt file. On Tue, Jun 12, 2012 at 5:31 PM, Villmow, Micah <Micah.Villmow at amd.com>wrote: > Add an optimization level and you get information.**** > > D:\ >opt -stats temp.bc -o tmp.bc2**** > > ** ** > > D:\ >opt -stats temp.bc -o tmp.bc2 -O3**** > > >
2009 Jun 11
1
[LLVMdev] Output to a DLL
When you say "spit bitecode from the JIT the first time, load it on subsequent sessions" : - do you want to write the IR in a file via BitcodeWriter and re-read it via BitcodeReader ? (you will pay the cost of native code emission on each load ?) - do you want to write the native code ? In that case, how do you retrieve the size of the buffer prepared by the
2009 Jun 11
0
[LLVMdev] Output to a DLL
"Nicolas Capens" <nicolas at capens.net> writes: Hello Nicolas. > I'd like to be able to write JIT-compiled code to a Windows DLL. I have no > idea where to start though. Does LLVM already offer some support for > this? Nope. Don't hold your breadth waiting for it. It is far from trivial to do. I don't know your requirements, but mine is to avoid
2011 Oct 31
1
[LLVMdev] Runtime optimization using llvm
Hello, I am getting to know how the Runtime Optimization feature of LLVM works and how I can use it. I want to know how I could print the results of any analysis and transformation pass. Say, I have a program written in c and I ran the edge-profiling pass onto it. Now I want to see the result. How could I do it? Also if I happen to change one of the passes inside folder
2011 Nov 14
0
[LLVMdev] llvm-gcc-i686-pc-linux-gnu-cross-arm-eabi-soft-float
Hello Devang, Please find attached the preprocessed source file and the LLVM bitecode. Hope this will help. Thanks Galina On Mon, Nov 14, 2011 at 9:48 AM, Devang Patel <dpatel at apple.com> wrote: > The buildbot > @ http://lab.llvm.org:8011/builders/llvm-gcc-i686-pc-linux-gnu-cross-arm-eabi-soft-float/builds/850 > is failing with following assertion failure. Is it possible for
2011 Nov 15
2
[LLVMdev] llvm-gcc-i686-pc-linux-gnu-cross-arm-eabi-soft-float
I filed PR 11378. Thanks! - Devang On Nov 14, 2011, at 1:27 PM, Galina Kistanova wrote: > Hello Devang, > > Please find attached the preprocessed source file and the LLVM > bitecode. Hope this will help. > > Thanks > > Galina > > > > On Mon, Nov 14, 2011 at 9:48 AM, Devang Patel <dpatel at apple.com> wrote: >> The buildbot >> @
2007 Jul 03
2
[LLVMdev] "bytecode" --> "bitcode"
I did this short experiment: ggreif at my [!297] cd /home/ggreif/llvm ggreif at my [!298] find . -name "*.cpp" | xargs grep bytecode | wc -l 143 I guess these are a quick prey for perl's in-place replace. But wait! There are more: ggreif at my [!299] find . -name "*.cpp" | xargs grep -i bytecode | wc -l 291 probably all of the rest is "Bytecode"
2007 May 06
3
[LLVMdev] goodbye bytecode, hello bitcode
I just checked in the final bits to switch us over from bytecode to bitcode. Old bytecode files will not work, but I expect this format to be stable going forward with the 2.x series of releases. This new format has a number of advantages. In particular: 1. The files are smaller. 2. The reader takes about 2/3 the memory it did before. 3. The reader is about 1/2 the code size of the old
2007 May 07
0
[LLVMdev] goodbye bytecode, hello bitcode
> Please let me know if you run into any problems. Documentation of the > file format is in the works. The bytecode support code is still in the > tree, but isn't being built. Assuming no major problems, I will remove > the old code tomorrow. I am getting a missing 'lib/Archive' directory when making from an updated CVS. Aaron
2011 Nov 02
0
[LLVMdev] debugger doesn't go inside the bitecode file
Hello, I am using gdb to debug the -instcount pass. The steps I followed were: 1. gdb opt 2. break llvm::PassManager::run 3. run -stats -analyze -instcount filename.bc I got the bc file using -emit-llvm option as following: llvm-gcc -O3 -emit-llvm filename.c -c -o filename.bc But when I started debugging, the debugger never really went into my bitecode file, filename.bc and it returned me the
2007 May 07
1
[LLVMdev] goodbye bytecode, hello bitcode
On Mon, 2007-05-07 at 21:12 +0100, Aaron Gray wrote: > > Please let me know if you run into any problems. Documentation of the > > file format is in the works. The bytecode support code is still in the > > tree, but isn't being built. Assuming no major problems, I will remove > > the old code tomorrow. > > I am getting a missing 'lib/Archive' directory
2013 Jan 03
2
simulation
Dear R users, suppose we have a random walk such as: v_t+1 = v_t + e_t+1 where e_t is a normal IID noise pocess with mean = m and standard deviation = sd and v_t is the fundamental value of a stock. Now suppose I want a trading strategy to be: x_t+1 = c(v_t – p_t) where c is a costant. I know, from the paper where this equations come from (Farmer and Joshi, The price dynamics of common
2009 Aug 14
1
Fwd: Re: rsyncd.conf chroot yes problem with symlink-ing
Ok it's now Solved ! In spite of trying all day long to figure it out what's wrong in my sintax i could find, ...using a pencile and a pice of paper, combining all commands parameters invoked so far and, came to the conclusion that -L does not stand with -l , think that i couldn't find in any docs or faq so far. Now, symlinks are being copied without a trouble. Tnks Paul for