search for: getnumparams

----- Original Message ----- > From: "James Molloy via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Vaivaswatha Nagaraj" <vn at compilertree.com> > Cc: "LLVM Dev" <llvm-dev at lists.llvm.org> > Sent: Thursday, December 3, 2015 4:41:46 AM > Subject: Re: [llvm-dev] Function attributes for LibFunc and its impact on GlobalsAA > >

...ction with bad signature", when my pass inserts a call to this function. But I don't have any problems with my pass if I run clang -emit-llvm -S, then llc and then gcc. With this approach I get a binary with my instrumentation inserted. This line causes a problem - assert((i >= FTy->getNumParams() || FTy->getParamType(i) == Args[i]->getType()) && "Calling a function with a bad signature!"); I tried to get a dump of FTy->getParamType(i) and Args[i]->getType(), but I wasn't able to do it in gdb - everytime I create a breakpoint it j...

...ple C program then I get the following exception: $ opt -o a.bc -load /data/llvm3.1/Release+Asserts/lib/Dat.so -MyPass < malloc.bc opt: Instructions.cpp:269: void llvm::CallInst::init(llvm::Value*, llvm::ArrayRef<llvm::Value*>, const llvm::Twine&): Assertion `(Args.size() == FTy->getNumParams() || (FTy->isVarArg() && Args.size() > FTy->getNumParams())) && "Calling a function with bad signature!"' failed. In older llvm, I had the following line: CallInst::Create(func, Opts, Opts , "", newBB); Which I have now modified for llvm3.1 to: Ca...

Dear All, I'm getting the following error building mainline llvm-gcc 4.2 (LLVM and llvm-gcc are up to date): cc1: /home/vadve/criswell/src/llvm22/lib/VMCore/Instructions.cpp:290: void llvm::CallInst::init(llvm::Value*, llvm::Value*): Assertion `(FTy->getNumParams() == 1 || (FTy->isVarArg() && FTy->getNumParams() == 0)) && "Calling a function with bad signature"' failed. Is anyone else seeing this? I get a similar error when compiling mainline llvm-gcc 4.0. -- John T.

...ts scalarized array operations function calls with *no arguments* simple common blocks Function calls with more than one argument don't work. Specifically: ..../gfortran funccall-1arg.f -o funccall-1arg.exe ..../llvm/lib/VMCore/Instructions.cpp:209: failed assertion `(Params.size() == FTy->getNumParams() || (FTy->isVarArg() && Params.size() > FTy->getNumParams())) && "Calling a function with bad signature!"' funccall-1arg.f: In function 'MAIN__': funccall-1arg.f:5: internal compiler error: Abort trap Please submit a full bug report, with preprocessed...

The first buildbot failure I can readily find was Monday, 26oct2009 around 7PM PDT. The assertion is Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i) == Params[i]->getType()) && "Calling a function with a bad signature!"), function init, file /Volumes/Sandbox/Buildbot/llvm/ build.llvm-gcc-x86_64-darwin10-selfhost/llvmCore.roots/llvmCore~obj/ src/lib/VMCore/Instructions.cpp, line 312. It s...

...is in fact fixed in current dragonegg svn. On a different question, what are the prospects getting aermod to compile under dragonegg? I am still seeing compile failures of the form... de-gfortran45 -ffast-math -funroll-loops -msse3 -O3 aermod.f90 -o aermod Assertion failed: ((NumParams == FTy->getNumParams() || (FTy->isVarArg() && NumParams > FTy->getNumParams())) && "Calling a function with bad signature!"), function init, file /sw/src/fink.build/llvm-clang-2.8-1/llvm-2.8/lib/VMCore/Instructions.cpp, line 242. *** WARNING *** there are active plugins, do not report...

...following exception: > > $ opt -o a.bc -load /data/llvm3.1/Release+Asserts/lib/Dat.so -MyPass < malloc.bc > > opt: Instructions.cpp:269: void llvm::CallInst::init(llvm::Value*, > llvm::ArrayRef<llvm::Value*>, const llvm::Twine&): Assertion `(Args.size() == > FTy->getNumParams() || (FTy->isVarArg() && Args.size() > FTy->getNumParams())) > && "Calling a function with bad signature!"' failed. > > In older llvm, I had the following line: > > *CallInst::Create(func, Opts, Opts , "", newBB);* > > Which I ha...

...on calls with *no arguments* > simple common blocks Great! > Function calls with more than one argument don't work. Specifically: > > ..../gfortran funccall-1arg.f -o funccall-1arg.exe > ..../llvm/lib/VMCore/Instructions.cpp:209: failed assertion > `(Params.size() == FTy->getNumParams() || (FTy->isVarArg() && > Params.size() > FTy->getNumParams())) && "Calling a function with bad > signature!"' > funccall-1arg.f: In function 'MAIN__': > funccall-1arg.f:5: internal compiler error: Abort trap > Please submit a full bug...

Hi all, I got a interesting problem when calling getNumOperands() of CallInst. For example, call void @_Z2f2PA100_i([100 x i32]* nonnull %arraydecay) If I use getNumOperands(), it will return 2. However, if I use getCalledFunction()->getNumParams(), it will return 1. According to the IR, I think the number of operands of the call instruction should be 1. I wonder what is going on for this situation. Thanks in advance for your time and suggestion! Best regards, Tingyuan LIANG MPhil Student HKUST -------------- next part -------...

When for example some call is wrong error message always looks like this: Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i) == Params[i]->getType()) && "Calling a function with a bad signature!"), function init, file /tmp/llvm-svn/llvm/lib/VMCore/Instructions.cpp, line 247. I believe assert() statements should better be replaced with more detailed printouts of what...

Hi! I have this error while building my code: Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i) == Params[i]->getType()) && "Calling a function with a bad signature!") Actually I'm trying to load functions from .bc file and use them in the code that I'm building with IRBuilder. I found that function parameter type is %struct.reValue*...

...//if this is a load if (isa<LoadInst>(i)) { //now i need to create an instruction that represents a call to a intrinsic Function* FIntr = Intrinsic::getDeclaration(&M, Intrinsic::regread_i32); // here it fails: void llvm::CallInst::init(llvm::Value*): //Assertion `FTy->getNumParams() == 0 && "Calling a function with bad signature"' failed. Instruction* Instr = CallInst::Create(FIntr); //do some stuff with the operands //and replace it ReplaceInstWithInst(i, Instr); } } Intrinsic regread_i32 is defined in Intrinsics.td as follows: //repre...

...This seems to work for functions without parameters (eg. int foo()), but once a function has a parameter I get the following assertion error: <llvmpath>/lib/VMCore/Instructions.cpp:297: void llvm::CallInst::init(llvm::Value*, llvm::Value* const*, unsigned int): Assertion `(i >= FTy->getNumParams() || FTy->getParamType(i) == Params[i]->getType()) && "Calling a function with a bad signature!"' failed. I've checked everything I can think of and it all seems correct to me ... Any help would be greatly appreciated! Thanks in advance, Marc Claesen

Hi all, I am creating a function and trying to call it using the LLVM API. It seems that whenever the function type includes an opaque-typed parameter, the CallInst::Create call causes an assert: Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i) == Params[i]->getType()) && "Calling a function with a bad signature!"), function init, file /usr/home/csanchez/shared/prj/tce/ src/llvm-2.5/lib/VMCore/Instructions.cpp, line 294. If I change the code so the function type has only non-opaque t...

...y, align 2, !dbg !1027 ret void return: ; preds = %entry ret void } opt: /home/vadve/aggarwa4/llvm27/llvm-2.7/lib/VMCore/Instructions.cpp:307: void llvm::CallInst::init(llvm::Value*, llvm::Value* const*, unsigned int): Assertion `(NumParams == FTy->getNumParams() || (FTy->isVarArg() && NumParams > FTy->getNumParams())) && "Calling a function with bad signature!"' failed. When I looked at the excption, it occurs when creating the CallInst. The type of the function being called at that point is still the old type, w...

On Oct 27, 2009, at 11:23 AMPDT, Stuart Hastings wrote: > The first buildbot failure I can readily find was Monday, 26oct2009 > around 7PM PDT. The assertion is > > Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i) > == Params[i]->getType()) && "Calling a function with a bad > signature!"), function init, file /Volumes/Sandbox/Buildbot/llvm/ > build.llvm-gcc-x86_64-darwin10-selfhost/llvmCore.roots/llvmCore~obj/ > src/lib/VMCore/Instructions.c...

...lInst::Create to construct a call to a variadic function, and I'm running into the following assertion failure: /localhome/simmon12/workspace/llvm-sources/lib/VMCore/Instructions.cpp:297: void llvm::CallInst::init(llvm::Value*, llvm::Value* const*, unsigned int): Assertion `(i >= FTy->getNumParams() || FTy->getParamType(i) == Params[i]->getType()) && "Calling a function with a bad signature!"' failed. I'm using the version of CallInst taking the beginning and end iterators of a vector<Value*>. I made sure to mark the function declaration with vararg...

...l, I downloaded LLVM to play with today and found that the BrainF example compiler fails with an assertion error like so: examples$ ./BrainF -jit /tmp/test.bf BrainF: Instructions.cpp:242: void llvm::CallInst::init(llvm::Value*, llvm::Value* const*, unsigned int): Assertion `(NumParams == FTy->getNumParams() || (FTy->isVarArg() && NumParams > FTy->getNumParams())) && "Calling a function with bad signature!"' failed. Aborted I tracked this down to bad arguments passed to the memset intrinsic. >From the svn logs it looks like the memset intrinsic was given a n...

Hi Jack, > I am finding that llvm 2.8 rc3 with dragonegg svn built against current > gcc-4_5-branch doesn't appear to allow gfortran to use -ffast-math. Attempting > to compile code using the dragonegg plugin under gcc 4.5.2 with that option produces the error... > > f951: Unknown command line argument '--enable-finite-only-fp-math'. Try: 'f951 -help' >