search for: numparams

...s. I can confirm this 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 activ...

...oid Verifier::visitIntrinsicFunctionCall(Intrinsic::ID ID, CallInst &CI) { Assert1(NumCallArgs >= 0, "gc.statepoint number of arguments to underlying call " "must be positive", &CI); - Assert1(NumCallArgs == (int)TargetFuncType->getNumParams(), - "gc.statepoint mismatch in number of call args", &CI); + const int NumParams = (int)TargetFuncType->getNumParams(); + if (TargetFuncType->isVarArg()) + Assert1(NumCallArgs >= NumParams, + "gc.statepoint mismatch in number of vararg...

...rrupt service routine interrupt(vector_number) attribute is rejected: __attribute__ ((interrupt(USCI_A0_VECTOR))) void ISR(void) { } error: 'interrupt' attribute parameter 48 is out of bounds This is due to the check in tools/clang/lib/Sema/SemaDeclAttr.cpp:5104 unsigned Num = NumParams.getLimitedValue(255); if ((Num & 1) || Num > 30) { S.Diag(AL.getLoc(), diag::err_attribute_argument_out_of_bounds) << AL.getName() << (int)NumParams.getSExtValue() << NumParamsExpr->getSourceRange(); return; } Also, the __...

...re i16 %tmp11, i16* %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...

Hi all, 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...

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

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' The standard gcc 4.5.2 gfortran compiler

...llvm-gcc4.2-2.4.source/gcc/testsuite/gfortran.dg/assumed_charlen_function_3.f90:14.25: function more_OK (ch, fcn) ! { dg-warning "is obsolescent in fortran 95 1 Warning: CHARACTER(*) function 'fcn' at (1) is obsolescent in fortran 95 Assertion failed: ((NumParams == FTy->getNumParams() || (FTy->isVarArg() && NumParams > FTy->getNumParams())) && "Calling a function with bad signature!"), function init, file /sw/src/fink.build/llvm-gcc42-2.4-1/llvm-2.4/lib/VMCore/Instructions.cpp, line 289. /sw/src/fink.build/llvm-gcc42-2...

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

Hola Jorge: Disculpa la tardanza pero me han tenido liado en otros menesteres. Yo no soy ni muchísimo menos un experto ni en series temporales ni en R de hecho retomo el tema después de muchos (demasiados) años aparcado y dedicándome a labores de programación pura y dura. Respecto a la diferencia de resultados con R y Statgraphics, no conozco el proceso de selección del modelo ARIMA que hace

...re i16 %tmp11, i16* %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...

...ed integer expressions ... llvm[4]: Compiling DeclSerialization.cpp for Release build DeclSerialization.cpp: In static member function 'static clang::FunctionDecl* clang::FunctionDecl::CreateImpl (llvm::Deserializer&, clang::ASTContext&)': DeclSerialization.cpp:521: warning: 'numParams' may be used uninitialized in this function .. llvm[2]: Linking Release Shared Library LTO.dylib *** Warning: Linking the shared library /code/llvm/Release/lib/ libLTO.la against the non-libtool *** objects /code/llvm/Release/lib/LLVMCppBackend.o /code/llvm/ Release/lib/LLVMMSIL.o /code/ll...