search for: llvmdc

...JIT or JIT with dwarf emission, but I do know that the LLVM exception design is being reconsidered for future releases (possibly 2.7?). Also, as noted in the wiki, please see: http://code.google.com/p/tart/ and http://www.incasoftware.de/~kamm/projects/index.php/2008/08/19/exception-handling-in-llvmdc-using-llvm/ for real world implementations. There are many others, as can be seen in the LLVM project page. Garrison On Jan 8, 2010, at 20:06, OvermindDL1 wrote: > On Fri, Jan 8, 2010 at 12:12 PM, Garrison Venn <gvenn.cfe.dev at gmail.com> wrote: >> I just added an exception exam...

Hi all, I'm having some trouble with inline asm expressions, more specifically how to create the right FunctionType for a given constraint set. So far it has worked well for inputs, but not for outputs. The inline asm support in this language (which is D, LLVMDC[1]) is through asm *statements*. I never have inline asm *expressions*, and outputs are always via memory. I D my test looks like this: extern(C) int printf(char*,...); int main() { int i = 12; printf("%d\n", i); asm { mov EAX, i; add EAX, EAX; mu...

...t(i32 0, i32 0) ret i32 %ret } This is based on the code in the language reference. If compiled and run on x86-64, it segfaults. After some talking to Chris on IRC, it seems as if fixing this is not a very high priority, and will not be for quite a long time. Now, I'm a hobbyist coder doing LLVMDC in my spare time. It's my first compiler projects and I had no knowledge whatsoever about compiler writing, the frontend I'm using or LLVM. That is I don't know very much about architecture intricacies, codegen parts of LLVM etc. This makes it a daunting task to try and fix LLVM va_arg...

...sion, but I do know that > the LLVM exception design is being reconsidered for future releases (possibly 2.7?). > > Also, as noted in the wiki, please see: > > http://code.google.com/p/tart/ and > http://www.incasoftware.de/~kamm/projects/index.php/2008/08/19/exception-handling-in-llvmdc-using-llvm/ > > for real world implementations. There are many others, as can be seen in the LLVM project page. I am one such non-unix platform, so if the example does not work for me, it is still as worthless as bad documentation for note...

...t; wrote: > Hi all, > > I'm having some trouble with inline asm expressions, more specifically > how to create the right FunctionType for a given constraint set. > So far it has worked well for inputs, but not for outputs. The inline > asm support in this language (which is D, LLVMDC[1]) is through asm > *statements*. > I never have inline asm *expressions*, and outputs are always via memory. > > I D my test looks like this: > > extern(C) int printf(char*,...); > int main() > { > int i = 12; > printf("%d\n", i); > asm >...

On Fri, Jan 8, 2010 at 12:12 PM, Garrison Venn <gvenn.cfe.dev at gmail.com> wrote: > I just added an exception example to the wiki intended to be run in a JIT environment. Although this information is heavily date dependent, > as the LLVM exception subsystem will be modified as time goes on, I could have used such an example when I was looking into this; hence the submission. >

I just added an exception example to the wiki intended to be run in a JIT environment. Although this information is heavily date dependent, as the LLVM exception subsystem will be modified as time goes on, I could have used such an example when I was looking into this; hence the submission. Having said this, I'm not an LLVM expert, and even though the code works, I'm sure there are

...l, >> >> I'm having some trouble with inline asm expressions, more specifically >> how to create the right FunctionType for a given constraint set. >> So far it has worked well for inputs, but not for outputs. The inline >> asm support in this language (which is D, LLVMDC[1]) is through asm >> *statements*. >> I never have inline asm *expressions*, and outputs are always via memory. >> >> I D my test looks like this: >> >> extern(C) int printf(char*,...); >> int main() >> { >> int i = 12; >> printf(&q...

What is the reason for llvm-gcc? Will regular gcc work (except for the releases that are broken, of course)? Does llvm in any way depend on features of llvm-gcc instead of gcc? Or is it optional? Was it conceived to give llvm itself a through shakedown? Is it there just in case you really want llvm code in some form from a C program? Is such llvm code necessary for some kind of use --

Hi Talin, > 1) I'm trying to figure out the relationship between the __cxa_throw > function, and the _Unwind_RaiseException function mentioned in the ABI doc. > My guess is that _Unwind_RaiseException is the language-neutral > implementation of stack unwinding, and __cxa_throw is the C++ exception > semantics that are implemented on top of it. If that is the case, should I >

Can you point out to me where in the VMKit code I should be looking? I spent some additional time reading the docs, and I have some specific questions: 1) I'm trying to figure out the relationship between the __cxa_throw function, and the _Unwind_RaiseException function mentioned in the ABI doc. My guess is that _Unwind_RaiseException is the language-neutral implementation of stack unwinding,