similar to: [LLVMdev] bitcode file format

On Thu, Jun 3, 2010 at 10:45 PM, Nehal Gandhi <nbg2k7 at gmail.com> wrote: >> Hi Eli, >> >> Thanks for that. Rookie mistake on my side. It solves the linking issue. >> However, it was not the main problem. The problem is when I execute the >> linked file ( modified bitcode + file containing the function), I get an >> assertion error - Assertion `Addr

On 13 June 2011 15:37, Cristian Zamfir <cristian.zamfir at epfl.ch> wrote: > Hello, > > Is it still possible to produce the LLVM bitcode after linking using the > LLVM gold plugin? > I get the warning "ld: warning: Ignoring flag also-emit-llvm" and the LLVM > bitcode is not dumped. > > I installed the LLVM gold plugin using the latest binutils from CVS and

Hello, [The first paragraph is safe to skip if you already know what PNaCl is.] The Portable Native Client (PNaCl) project is a toolchain for producing portable bitcode from C and C++ code and running in securely and efficiently on the web via Native Client. For more details see this presentation from the last Google I/O: https://developers.google.com/events/io/sessions/325679543and

On Fri, Jun 4, 2010 at 12:09 AM, Nehal Gandhi <nbg2k7 at gmail.com> wrote: > On Thu, Jun 3, 2010 at 10:45 PM, Nehal Gandhi <nbg2k7 at gmail.com> wrote: >>> Hi Eli, >>> >>> Thanks for that. Rookie mistake on my side. It solves the linking issue. >>> However, it was not the main problem. The problem is when I execute the >>> linked file (

Hi Eli, I have attached a tar file containing Pass (ConditionPass.cpp), External function (PrintRes.cpp) and test program (try.c). I use command chain as describe in previous mail. Thanks, Nehal. -----Original Message----- From: Eli Friedman [mailto:eli.friedman at gmail.com] Sent: Friday, June 04, 2010 3:39 AM To: Nehal Gandhi Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Inserting a

Am 19.06.2013 18:01, schrieb JF Bastien: > > From the provided documentation I understood that in memory data > structures of a PNaCl program are incompatible to the host program > because ABIs are different (e.g. PNaCl pointers are always 32-bit > even when running on x86_64 platform). > So PNaCl program can't access any data structures of the host >

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 > >

Hello, Is it still possible to produce the LLVM bitcode after linking using the LLVM gold plugin? I get the warning "ld: warning: Ignoring flag also-emit-llvm" and the LLVM bitcode is not dumped. I installed the LLVM gold plugin using the latest binutils from CVS and LLVM 2.6, since I read on the discussion list that this was possible with LLVM 2.6. This is the command I use:

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,

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, I've discovered a few things I want to ask about. I notice the Bitcode format documentation [0] is

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,

Hi Eli, Thanks for that. Rookie mistake on my side. It solves the linking issue. However, it was not the main problem. The problem is when I execute the linked file ( modified bitcode + file containing the function), I get an assertion error - Assertion `Addr && "Code generation didn't add function to GlobalAddress table!"' failed. So my main concern - is that a

Hi All, I am trying to write code for simple instrumentation. What I want to do is to insert a call to an external function for result of each conditional branch instruction. This external function simply print true or false based on the result of condition. The modified code is then written into new file. However when I try to link that file with another bitcode file (containing external

I tried to install the SAFECode in LLVM 2.6 following the instruction in Install.html. But when I do the step: # cd projects/poolalloc # make I get the errore below: llvm[2]: Compiling qsort.c for Release build (bytecode) llvm[2]: Compiling strdup.c for Release build (bytecode) llvm[2]: Compiling qsort.c for Release build llvm[2]: Compiling strdup.c for Release build llvm[2]: Compiling qsort.ll

On Thu, Jun 3, 2010 at 10:45 PM, Nehal Gandhi <nbg2k7 at gmail.com> wrote: > Hi Eli, > > > > Thanks for that. Rookie mistake on my side. It solves the linking issue. > However, it was not the main problem. The problem is when I execute the > linked file ( modified bitcode + file containing the function), I get an > assertion error - Assertion `Addr &&

Hi All, I hope to get some information about functions in a bitcode file. Say, if we have a function foo(), and the bitcode file is generated by a single source file, then I want to get the line number foo() locates in that source file. If the bitcode file is linked by multiple bitcode files, is it possible to also get which file foo() locates in? Thanks, Chen -------------- next part

Hello, My partner and I am making a small app needs to access a C++ library from the LLVM 2.5 JIT. We've made sure that there are no classes and have put 'extern "c"' in front of the functions we need to access. In order to make this work, we seem to need to have a bitcode version of libstdc++ so we can avoid writing our own implementations of std::string and std::vector.

> The document is available as a PDF here: > https://docs.google.com/a/chromium.org/viewer?a=v&pid=sites&srcid=Y2hyb21pdW0ub3JnfGRldnxneDo0OWYwZjVkYWFjOWNjODE1 > > And in text here: > https://sites.google.com/a/chromium.org/dev/nativeclient/pnacl/stability-of-the-pnacl-bitcode-abi First, sorry for jumping in an old thread. I had this marked but had not been able to read it

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

On Thu, Jun 3, 2010 at 9:43 PM, Nehal Gandhi <nbg2k7 at gmail.com> wrote: > Hi All, > > > > I am trying to write code for simple instrumentation. What I want to do is > to insert a call to an external function for result of each conditional > branch instruction. This external function simply print true or false based > on the result of condition. The modified code is