Varargs Code Triggers Assertion

[llvmbot]

Bugzilla Link	2214
Resolution	WORKSFORME
Resolved on	Nov 07, 2018 00:22
Version	trunk
OS	MacOS X
Attachments	Preprocessed source code that triggers assertion
Reporter	LLVM Bugzilla Contributor

Extended Description

I get the following assertion when compiling the attached code with llvm-g++ on Darwin 9.2.0 on PowerPC:

/Users/criswell/box/ppc/llvm-gcc4/bin/llvm-g++ -emit-llvm -S test.i

/Users/criswell/src/llvm22/lib/VMCore/Instructions.cpp:290: failed assertion `(FTy->getNumParams() == 1 || (FTy->isVarArg() && FTy->getNumParams() == 0)) && "Calling a function with bad signature"'
test.cpp: In function 'void funccheck(unsigned int, void*, void*, ...)':
test.cpp:17: internal compiler error: Abort trap
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://llvm.org/bugs for instructions.

The test case is attached.

[llvmbot]

I don't see this on x86-32 linux.

[llvmbot]

Works for me with a compiler built Apr 9. I'll check if something broke overnight.

[llvmbot]

Nope, still works for me.

[llvmbot]

I figured out the problem.

I had reconfigured my build tree but neglected to specify the correct program-prefix option; this resulted in both old and new binaries in my llvm-gcc installation directory. Naturally, I was using the old ones.