search for: printfunction

...ds name 99.4 545.84 0.0 0.00 "myf" 95.2 522.70 0.0 0.06 "myg" 90.7 498.20 0.0 0.02 "standardGeneric" 90.6 497.70 0.0 0.00 "print" 90.5 497.32 5.3 29.06 "printFunction" 90.5 497.32 0.0 0.00 "print.trellis" 62.7 344.58 62.6 343.96 "lattice.setStatus" ... % self % total self seconds total seconds name 62.6 343.96 62.7 344.58 "lattice.setStatus"...

...ouble X) { printf("%f\n", X); } // Args type std::vector<const Type*> args(1, Type::getDoubleTy(getGlobalContext())); // return void, 1 arg double, no varargs FT = FunctionType::get(Type::getVoidTy(getGlobalContext()), args, false); // creating stub for print function Function* printFunction = Function::Create(FT, Function::ExternalLinkage, "print", module); By doing this (and the variable declaration below), my IR is: ; ModuleID = 'example' define void @main() { entry: %var = alloca double ; <double*> [#uses=1] store double 1.0...

I think you might have to provide an empty list if your function doesn't take parameters. Maybe using an irbuilder would help? -bw On Aug 22, 2009, at 2:13 PM, Renato Golin <rengolin at systemcall.org> wrote: > 2009/7/4 Albert Graef <Dr.Graef at t-online.de>: >> This is all I ever needed to interface to C functions using LLVM. >> It's >> really

2009/7/4 Albert Graef <Dr.Graef at t-online.de>: > This is all I ever needed to interface to C functions using LLVM. It's > really easy. Of course you still need a prototype of the external > function (function definition without body) in your IR, but that's it. Hi Albert, I'm having a similar problem and I found I can't declare the function and use it, most likely

I fell over this issue yesterday myself with lots of asserts being thrown. I think the issue is in lib/IR/AsmWriter.cpp:1618 in the function AssemblyWriter::printFunction(const Function *F) Looking at the code I think the 2nd for loop should be preceded by the test ... if (Idx < AS.getNumSlots()) Not sure why it doesn't fail on other platforms as it looks like it should be a genuine issue on all platform. That change significantly reduced the failures...

Hi, I check-out the latest version of LLVM and see many failures (on Win64): ******************** 67> FAIL: LLVM :: Transforms/GlobalOpt/zeroinitializer-gep-load.ll (5518 of 7763) 67> ******************** TEST 'LLVM :: Transforms/GlobalOpt/zeroinitializer-gep-load.ll' FAILED ******************** 67> Script: 67> -- 67> W:/LLVM_org/build64/bin/Debug/opt.EXE <

...t. Please fix. Sent from phone On Apr 29, 2013 8:41 AM, "Keith Walker" <keith.walker at arm.com> wrote: > I fell over this issue yesterday myself with lots of asserts being thrown. > > I think the issue is in lib/IR/AsmWriter.cpp:1618 in the function > AssemblyWriter::printFunction(const Function *F) > > Looking at the code I think the 2nd for loop should be preceded by the test > ... > > if (Idx < AS.getNumSlots()) > > Not sure why it doesn't fail on other platforms as it looks like it should > be a genuine issue on all platform. > > T...

In a debug build you should get a stack trace by default, which would be helpful here. I can try to repro later today, but I'm not surprised there are issues because most people I know stick with 32-bit builds even on 64-bit Windows. On Mon, Apr 29, 2013 at 4:27 AM, Demikhovsky, Elena <elena.demikhovsky at intel.com> wrote: > Hi, > > > > I check-out the latest version of