assigned to @lattner

The reason that you get the:
WARNING: While resolving call to function '__stdio_outs' arguments were dropped!

warnings is because you are relying undefined behavior. In vprintf you cast __stdio_outs to take three
parameters. __v_printf passes three arguments to it, but __stdio_outs only takes two arguments.

LLVM "devirtualizes" the function pointer, turning it into a direct call, at which point it sees that you're
passing three arguments (the third being fn->data) instead of two. You should really change
__stdio_outs to take three arguments.

However, there is still an llvm bug. I'm investigating.

-Chris

The bug is in your code. This is not valid LLVM:

void %llvm.memcpy.i32(sbyte*, sbyte*, uint, uint) {
entry:
ret void
}

You've turned memcpy and others into a noop. I will make the verifier reject this. What are you trying to
accomplish?

Fixed, patch here:
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20061211/041334.html

Testcase here:
Verifier/2006-12-12-IntrinsicDefine.ll

-Chris

My purpose for defining intrinsics is to eliminate all declares from the final linked bytecode.
Declares are not handled by our compiler, so I need to resolve all of them.
I will fix the problem by writing C definitions for the intrinsics, and renaming them by hand.
That will allow me to link them in.
Thanks for all your help!

another solution is to handle intrinsics like llvm.mempcy.* as calls to memcpy.

-Chris

Yes, after some discussion we decided to do it that way.
Thanks again for your help!

I have made the two changes you mentioned.
I got rid of llvm.o which re-defined intrinsics.
Shame on me for doing that in the first place!
Also, __stdio_puts() now has a thrid parameter.

However, the problem still exists.

tail call void (int, ...)* %printf( int 0 )
This problem is only apparent when using optimizer passes.

Am I still doing something stupid?
Should I open a new bug report and let you close this one?

I uploaded llvm-bug2.zip (see bug URL) so you can see it for yourself.

Ok, I just talked to nicholas, and he realized that the string literal is being accessed directly in printf()
instead of being passed as an argument.

So, I was chasing a red haring. Sorry!!

I set the bug back to fixed.