search for: yipe

gafferuk <gafferuk at gmail.com> writes: > Im confused. The function i wish to call is a return type of int. > Im calling it with int dd = yipee(1); > > What's wrong? Declare the function: int yipee(int); int main() { int dd = yipee(1); return 0; } If that still crashes, put a breakpoint on `yipee' and see if the execution gets there, if the argument is right, if the crash happens inside the function or after it...

> when I run my app the compiler says: > E:\Projects\Whistle\Whistle\Release>Whistle file.c > file.c(3) :  warning: implicit declaration of function 'yipee' is invalid in > C99 > >      [-Wimplicit-function-declaration] >    int dd = yipee(1); >             ^ This way you're creating a call to variadic function. It's of different type compared to function you're binding to. -- With best regards, Anton Korobeynikov Fac...

I tried what you said, now I get: LLVM ERROR: Program used external function 'yipee' which could not be resolved! Stack dump: 0. Running pass 'X86 Machine Code Emitter' on function '@main' did not even get as far as a breakpoint. Óscar Fuentes wrote: > > gafferuk <gafferuk at gmail.com> writes: > >> Im confused. The function i wi...

...de "llvm/Support/ManagedStatic.h" #include "llvm/Support/raw_ostream.h" #include "llvm/System/Host.h" #include "llvm/System/Path.h" #include "llvm/Target/TargetSelect.h" using namespace clang; using namespace clang::driver; extern "C" int yipee(int val) { fprintf(stderr, "yipee!"); return 1; } llvm::sys::Path GetExecutablePath(const char *Argv0) { // This just needs to be some symbol in the binary; C++ doesn't // allow taking the address of ::main however. void *MainAddr = (void*) (intptr_t) GetExecutablePath; retu...

Im confused. The function i wish to call is a return type of int. Im calling it with int dd = yipee(1); What's wrong? Anton Korobeynikov-2 wrote: > >> when I run my app the compiler says: >> E:\Projects\Whistle\Whistle\Release>Whistle file.c >> file.c(3) :  warning: implicit declaration of function 'yipee' is invalid >> in >> C99 >> >&...

...m::Type::getInt32Ty(llvm::getGlobalContext()), std::vector<const llvm::Type*>(1, llvm::Type::getInt32Ty(llvm::getGlobalContext())), false); when I run my app the compiler says: E:\Projects\Whistle\Whistle\Release>Whistle file.c file.c(3) : warning: implicit declaration of function 'yipee' is invalid in C99 [-Wimplicit-function-declaration] int dd = yipee(1); ^ 1 warning generated. LLVM ERROR: Program used external function 'yipee' which could not be resolved! Stack dump: 0. Running pass 'X86 Machine Code Emitter' on function '@m...

hi, im creating a music application(image below). At the moment im using tcc compiler but im moving across to clang because of the improved compiler warnings. Can anyone please explain and show code so I can use clang's JIT to call functions in my application? Thanks. http://old.nabble.com/file/p29449300/51709341.jpeg -- View this message in context:

gafferuk <gafferuk at gmail.com> writes: > Can someone pease tell me what I am doing wrong? It is hard to say because you don't say what the problem is, but let's try. > Im trying to register an external function with the JIT, so can call > functions in my music > > application. > > Here my function > > int Execute(llvm::Module *Mod, char * const *envp)

...uctions in my music application from c code which will be used by the JIT. Here my function, i have made no other changes to the clang interpreter example. Can you see anything else I have to add to either the fuction below or to the c code to be JIT at the bottom? // function I wish to call. int yipee(int aVar) { aVar = 5; } int Execute(llvm::Module *Mod, char * const *envp) { llvm::InitializeNativeTarget(); std::string Error; llvm::OwningPtr<llvm::ExecutionEngine> EE( llvm::ExecutionEngine::createJIT(Mod, &Error)); if (!EE) { llvm::errs() << "unable to make e...

On Aug 17, 2010, at 1:56 PM, gafferuk wrote: > > hi, im creating a music application(image below). > > At the moment im using tcc compiler but im moving across to clang because of > the improved compiler warnings. > Can anyone please explain and show code so I can use clang's JIT to call > functions in my application? You'll probably want to take a look at the

...-- llvm::FunctionType* ft = llvm::FunctionType::get(llvm::Type::getInt32Ty (llvm::getGlobalContext()), std::vector<const llvm::Type*>(0, llvm::Type::getInt32Ty (llvm::getGlobalContext())), false); llvm::Function* f = llvm::Function::Create(ft, llvm::Function::ExternalLinkage, "yipee", Mod); EE->addGlobalMapping(f, yipee); llvm::Function *YipeeFn = Mod->getFunction("yipee"); if (!YipeeFn) { llvm::errs() << "'yipee' function not found in module.\n"; return 255; } // end code I have added -----------------------------------...

Vikram, I also agree with you. I understand that target-independent representation is very valuable and important for software compilation. However, when we are doing high-level synthesis (also called behavioral/architectural synthesis), the targeting architecture is also changing. That is, we need to do architecture exploration and the IR transfromation simultaneously. For example,

Yeah. We need to have more extra fields in the instruction. Fo example, during high-level synthesis, we must schedule an instruction to a certain control step (or cycle), and bind it to be execute on a certain functional unit, etc. Besides the in-memory exchange of the information, we also want on-disk exchange. That introduces the write-out/parse-in problem. Thanks ----- Original Message -----

Yiping, If you are doing architectural synthesis, I do agree that you likely need to capture some operations in the instruction set, especially if you want to perform analyses and optimizations on those operations. Some specific comments: On Oct 20, 2004, at 6:04 PM, Yiping Fan wrote: > Vikram, >     I also agree with you. I understand that target-independent > representation is

I just picked up 3.10-pre15 and the "PXELINUX corrupts graphic filename referenced from DISPLAY file" bug is zapped. Yipee! Thanks hpa. And Arwin too, if that 'xor esi,esi' was the crux. However, LOCALBOOT -1 and LOCALBOOT 0 don't work the same as they did for me in 3.07. :-( 3.07: LOCALBOOT -1 apears to work as I have a hard disk listed in bios boot order after the net card. LOCALBOOT 0 also works...

I'm CC'ing the llvm-dev list because other people are more knowledgeable about the bytecode format/encoding than I am. Please follow-up the replies to the list. On Wed, Oct 20, 2004 at 11:27:53AM -0700, Yiping Fan wrote: > We also want to extend the llvm instructions/intrinsic > functions/types/passes to support our high-level synthesis for > hardware. First of all, we want to

Yiping, Could you describe in a little more detail what your goals are? I agree with Reid and Misha that modifying the instruction definition is usually not advisable but to suggest alternatives, we would need to know more. Also, for some projects it could make sense to change the instruction set. --Vikram http://www.cs.uiuc.edu/~vadve http://llvm.cs.uiuc.edu/ On Oct 20, 2004, at 2:41 PM,

On Wed, Oct 20, 2004 at 11:59:45AM -0700, Yiping Fan wrote: > Yeah. We need to have more extra fields in the instruction. Fo > example, during high-level synthesis, we must schedule an instruction > to a certain control step (or cycle), and bind it to be execute on a > certain functional unit, etc. Since we're talking about "execution" and "scheduling", you

Hi, Yiping! I am not sure of the answer to your question, but I am forwarding it to the LLVMdev list where I am sure someone will be able to answer you. Please send development questions directly to LLVMdev and you will get a response quicker, as it is read by many LLVM developers. ----- Forwarded message from Yiping Fan <fanyp at cs.ucla.edu> ----- Date: Mon, 31 Oct 2005 17:20:24 -0800

Hello, I have a perl program which produces the input. Instead of print it to a file then let R read the file, I want to let R to read the input directly from the perl output, I am using a PERL IPC::open2 module for this, local (*Read,*Writer); $pid = open2(\*Read, \*Writer, "R --no-save --slave< my.R") #input to R for(){ print Writer data; } close Writer; #R output