search for: aosabook

I have a requirement where I want a Fact to be stored in PuppetDB during the manifest run and not during the initial fact gathering phase. I know I can, in my manifests, create a file in /etc/facter/facts.d or I can write a Ruby script that will then be distributed by plugin sync. But both of these methods will only publish the fact during the initial phase of the puppet agent run. What I

...ct of such a representation on mixing code from different languages. Suppose we have a huge library X written in language LX, which we would be able to use from our program Y written in language LY. If both LX and LY are supported by LLVM would that be difficult? Regards Giovanni [1] http://www.aosabook.org/en/llvm.html -- Giovanni [dacav] Simoni <giovanni.simoni at roundhousecode.com> <simgidacav at gmail.com>

...eful about portability and it's OK. With LLVM IR I will have to take the target platform into consideration when I compile. > > This leads to my second question, what is the true goal of LLVM IR? I feel like some people are disagreeing on this aspect. Here is an introduction: http://www.aosabook.org/en/llvm.html It has this to say about generating C code: "Unfortunately, doing this prevents efficient implementation of exception handling, provides a poor debugging experience, slows down compilation, and can be problematic for languages that require guaranteed tail calls (or other feat...

Hello, I am a computer science student new to LLVM compiler infrastructure. Please guide me where to start from to learn LLVM in the most effective way. Thanks, Siddharth Shankar Swain -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170115/6855d875/attachment.html>

Hi, wanting to build up some language of my own, I have always thought about feeding my compiler output to a C compiler like gcc or clang, however when I learned about (considered using) LLVM IR I immediately thought it could be of some help. LLVM doesn't seem to be portable though, some people seem to say "If you are generating C then why not go all the way and generate some

On Mon, 13 Jan 2020 at 06:50, Eric Christopher <echristo at gmail.com> wrote: > I don't really consider this addressed without a plan of action (before merge) that contains a list of standard llvm support libraries that would be used in addition to things being removed (pretty much all use of C++ c* headers and more?) as well as staffing and approximate ETAs. Agreed. > I think