similar to: [LLVMdev] "\01__isoc99_fscanf"

On 29 May 2010 02:43, Ryan M. Lefever <lefever at illinois.edu> wrote: > I have a bitcode file Y that has a symbol  __isoc99_fscanf in it.  When > I disassemble the bitcode, the symbol is written as > "\01__isoc99_fscanf".  I am wondering where this symbol is coming from? >  I grep'ed throughout /usr on my machine for both names, and I only > found

> While testing a File I/O sample program, I've encountered a link failure due > to missing implementation of "\01__isoc99_fscanf" function. I think this > function should be named "__isoc99_fscanf" instead. Please see the program > code and LLVM IR generated by DragonEgg and clang below. It shows that clang > generates "__isoc99_fscanf", while

Dear all, First of all, Merry Christmas! :) While testing a File I/O sample program, I've encountered a link failure due to missing implementation of "\01__isoc99_fscanf" function. I think this function should be named "__isoc99_fscanf" instead. Please see the program code and LLVM IR generated by DragonEgg and clang below. It shows that clang generates

I am writing a transformation that needs to add a call to a function F() at the beginning of main() with the addresses of argc and argv as parameters to F(). However, the bytecode file I'm transforming has not allocated space on the stack for argc and argv. So, I developed my transformation to change main() from: ----- int main(int %argc, sbyte** %argv){ entry: ... // some use of

After looking at this problem longer, I believe that there is something wrong with the disassembler. When I run my transformation and then disassemble the output, I get bytecode that looks like: ----- int %main(int %argc, sbyte** %argv) { entry: alloca int ; <int*>:0 [#uses=3] alloca sbyte** ; <sbyte***>:0 [#uses=3] store int %argc,

Hello, Ryan. > It seems as though, when the bytecode is disassebled, the result of the > allocas should be given as a parameter to the stores. It's given. > If the disassembler doesn't give the allocas a name, then that dependency is > not conveyed. Both disassembly & bytecode is correct. Please carefully read LLVM Language reference about %"num" names. --

I am trying to disassemble some bytecode using llvm-dis: llvm-dis -f -o llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc However, I am getting the following error. llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) How do I go about figuring out what the problem is? llvmtest/sliceme2.cbc is newly compiled using the same version of llvm-gcc as llvm-dis. -- Ryan M. Lefever

I am trying to use llvm-ld but when I try to link several bytecode files into a single bytecode file, it gives me the following error: llvm-ld -o benchmarks/bc-1.06/src/bc.c.bc benchmarks/bc-1.06/src/bc.i.bc benchmarks/bc-1.06/src/execute.i.bc benchmarks/bc-1.06/src/getopt1.i.bc benchmarks/bc-1.06/src/getopt.i.bc benchmarks/bc-1.06/src/global.i.bc benchmarks/bc-1.06/src/load.i.bc

I was able to correct this problem by checking out the latest version of llvm-gcc4 from svn and compiling it from source. One note, in order to get llvm-gcc4 to compile, I had to add #include "llvm/Analysis/LoopPass.h" to gcc/llvm-backend.cpp Ryan M. Lefever wrote: > I get a similar error when I try to disassemble a bytecode file > generated by llvm-gcc released for llvm

I get a similar error when I try to disassemble a bytecode file generated by llvm-gcc released for llvm 1.9. Do I need to upgrade to a new llvm-gcc? Ryan M. Lefever wrote: > I am trying to use llvm-ld but when I try to link several bytecode files > into a single bytecode file, it gives me the following error: > > llvm-ld -o benchmarks/bc-1.06/src/bc.c.bc

Hi Ryan, On Fri, 2006-12-01 at 18:06 -0600, Ryan M. Lefever wrote: > I am trying to disassemble some bytecode using llvm-dis: > llvm-dis -f -o llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc > > However, I am getting the following error. > > llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) The problem is most likely that sliceme2.cbc is *not* bytecode. Open the

> Why isn't llvm giving a name to the value returned by the allocas and > using it in the store instructions? Because you pass in an empty string for the name in the new AllocaInst calls below. Replace the empty strings with "argc_addr" or whatever you want. > AllocaInst* argc_alloca = new AllocaInst(argc->getType(), "", >

I am running asterisk 1.4 and the Digium GUI SVN-branch-2.0-r4489. When one phone calls another, I see the following on the console (here, 6223 dials 6123) -- Executing [6123 at DLPN_DefaultDialPlan:1] Macro("IAX2/6223-10489", "stdexten|6123|SIP/6123&IAX2/6123") in new stack -- Executing [s at macro-stdexten:1] Set("IAX2/6223-10489",

About thirty minutes ago I started an update. Everything downloaded fine. But when it came to "Running Transaction", it hung: .... Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating : xulrunner 1/18 And there it sits still. There's plenty of disk space. The load on the CPU is under

To what do variable size LLVM alloca instructions get translated, when they are turned into machine code? I compiled a piece of code to bitcode and disassembled it. The disassembled code showed that there were alloca instructions with variable-sized parameters within the bitcode. When I turned the bitcode into machine code, I performed an nm on the result but didn't see any symbols

On my 32 bit linux box, things seam to work find, but on my 64 bit linux box I am getting problems. I have the following c file (lib.c): -------------------------------- #include <stdio.h> void libmethod(){ printf("libmethod()\n"); } ------------------------------- I tried to get a shared library using the following commands: llvm-gcc -emit-llvm -Wall -fPIC -c -o lib.opt.bc

Hi R developers, On R-devel (2020-06-24 r78746) I am getting those two new exceptions during R check. I found a change which eventually may be related https://github.com/wch/r-source/commit/69de92b9fb1b7f2a7c8d1394b8d56050881a5465 I think this may be a regression. I grep'ed package manuals and R code for unique.default but don't see any. Usage section of the unique method looks fine as

I am rsyncing and remotely doing some work based on a logfile from a windows box from a centos backup server. I get the output from a vss snapshot that has a section like this: * SNAPSHOT ID = {639ef5df-c933-4496-878a-ed57b9d52876} ... - Shadow copy Set: {427ac5db-21be-4c53-8ca4-24e7bac86a1d} - Original count of shadow copies = 2 - Original Volume name:

CVS ( yesterday's version ) ogg/autogen.sh fails because of AM_PROG_LIBTOOL ( Macro is not found )... I use automake 1.4 ( SuSE 6.3) I grep'ed all m4 library, but could not find it. Where can I found a list of tools needed to compile current CVS version. Thanx Roman Razilov --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/