search for: stronlgly

...for : interfacing with C. The most common hurdle with calling C from managed : code is interfacing with the garbage collector. The C interface was : designed to require very little memory management, and so is : straightforward in this regard. Evidently I have to go look in include/llvm-c, since I stronlgly suspect you didn't go to the trouble of writng a C wrapper for anything that wasn't needed by an LLVM user. Anything internal you'd have left in C++. So the API for a C++ *user* could be described as "those parts of the internals API that happen to be used in implementing llvm...

...ost common hurdle with calling C from > managed > : code is interfacing with the garbage collector. The C interface was > : designed to require very little memory management, and so is > : straightforward in this regard. > > Evidently I have to go look in include/llvm-c, since I stronlgly > suspect > you didn't go to the trouble of writng a C wrapper for anything that > wasn't needed by an LLVM user. Anything internal you'd have left in > C++. > > So the API for a C++ *user* could be described as "those parts of the > internals API that hap...

On Apr 28, 2008, at 17:32, Hendrik Boom wrote: > In http://llvm.org/docs/FAQ.html, when taking about writing a compiler > that uses LLVM (at least I think that's what the FAQ question is > asking), > the FAQ recommends > >> # Call into the LLVM libraries code using your language's FFI >> (foreign >> function interface). >> >> * for:

In http://llvm.org/docs/FAQ.html, when taking about writing a compiler that uses LLVM (at least I think that's what the FAQ question is asking), the FAQ recommends > # Call into the LLVM libraries code using your language's FFI (foreign > function interface). > > * for: best tracks changes to the LLVM IR, .ll syntax, and .bc > format > * for: