similar to: [LLVMdev] "Mapping High-Level Constructs to LLVM IR"

On Fri, Nov 22, 2013 at 10:25 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi guys, > > I have begun writing on a new document, named "Mapping High-Level > Constructs to LLVM IR", in which I hope to eventually explain how to map > pretty much every contemporary high-level imperative and/or OOP language > construct to LLVM IR. > > I write it for two

On 11/22/2013 9:25 PM, Mikael Lyngvig wrote: > Hi guys, > > I have begun writing on a new document, named "Mapping High-Level > Constructs to LLVM IR", in which I hope to eventually explain how to > map pretty much every contemporary high-level imperative and/or OOP > language construct to LLVM IR. > > I write it for two reasons: > > 1. I need to know

Thanks, you have a lot of valid points there. I have myself long ago abandoned the path of using C as a backend language due to the very factors you mention. However, as I said, the document was put together in 30 minutes. Not exactly ready for prime time :-) I do agree that all of the things you mention should be described, including Lambdas, closures, and generators, but I must admit up

Yes, it is sort of scary that there seems to be no definite resource to consult for information on especially advanced OOP things. I have something like 20 compiler books on my shelves and yet none of them mention a single word on how to implement multiple inheritance, exception handling, or interfaces. It seems like they are all happy about presenting a subset of Pascal, or Java, with an

Hi, documentation is always good and this is a great idea. It'll be particularly useful as a place where additional examples of constructs from non-C-family languages could be added (since most compiler tutorials inevitably focus on languages that are a lot like C/C++/Obj-C). I'd imagine you've already thought of this, but it might be something where using pseudo-LLVM-IR is of the

Hi David, I'm glad you like the idea :-) I've been busy and so far only lack about three or four things in the C++ area of features: Proper exception handling (which I need to understand myself first), closures (which I don't think I've ever used), and generators (which I always wondered how they were implemented). I think you are absolutely right - some day, this document will

I'm glad you see the potential of this document. It is very important that everybody joins in and add their pennies so that the document eventually reflects the real experience of people who have actually tried and studied these things, and who are familiar with LLVM IR from using and implementing it for a long time. I sort of hope that this document will one day cover almost all LLVM IR

On Sat, Nov 30, 2013 at 11:20 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > I'm glad you see the potential of this document. It is very important > that everybody joins in and add their pennies so that the document > eventually reflects the real experience of people who have actually tried > and studied these things, and who are familiar with LLVM IR from using and

Hi, It will probably take a few weeks or a month before the "Mapping High-Level Constructs to LLVM IR" document is ready for prime time. Until then, you can review and study it at this URL: https://github.com/archfrog/llvm-doc/blob/master/MappingHighLevelConstructsToLLVMIR.rst Please notice that I specifically do not advocate reviewing the document for a week or two. But feel free

Just briefly looking over the document, I really like the content. I'm now starting to see a really good "fit" for this document: a "guide for language frontend implementers" illustrating basic techniques along with a discussion of implementation decisions regarding the lowering of certain constructs. I don't think that we currently have any documentation targeted at

Hi Chris, Thanks for the supporting words! I'm pushing the document both for egoistic motives (like so many others, I'll learn a ton from this document) and for altruistic motives - the easier it is to implement a new language, the more interesting and highly well-thought out languages we will see in the future. And I see it as my purpose, as a mostly black-box user of LLVM, to enhance

On Nov 28, 2013, at 6:07 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi, > > It will probably take a few weeks or a month before the "Mapping High-Level Constructs to LLVM IR" document is ready for prime time. Until then, you can review and study it at this URL: > >

On Wed, Dec 4, 2013 at 12:54 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Chris, > > Thanks for the supporting words! I'm pushing the document both for > egoistic motives (like so many others, I'll learn a ton from this document) > and for altruistic motives - the easier it is to implement a new language, > the more interesting and highly well-thought

Hi Philip, Thanks for your great list of ideas for the document! I don't really have a scope for the document beyond: If it something that requires mapping from high-level to LLVM IR, I think it should go into the document. I started out using C++ examples because many people know C++. I am personally mostly an advocate of statically checked languages but I don't see that as a reason

On 11/23/2013 12:18 AM, Mikael Lyngvig wrote: > Thanks, you have a lot of valid points there. I have myself long ago > abandoned the path of using C as a backend language due to the very > factors you mention. > > However, as I said, the document was put together in 30 minutes. Not > exactly ready for prime time :-) > > I do agree that all of the things you mention

I have a significant chunk of notes from my experience with garbage collector integration with LLVM that I'd be happy to contribute to this effort. The original notes live here: https://code.google.com/p/epoch-language/wiki/GarbageCollectionScheme I imagine it would be preferred if that document was formatted and edited to match the existing efforts; I'll try and start converting it over

Hi, This may be a daft question, but I have just begun taking a serious look at LLVM for a project that I am working on. Knowing myself pretty well, the probability that I ever complete the project is infinitesimal. I am saying this so you don't jump up out of your chair, yelling "HOORAY!" because I am considering to use LLVM. Think of me as an academic student with too much

On 11/28/13 6:07 PM, Mikael Lyngvig wrote: > Hi, > > It will probably take a few weeks or a month before the "Mapping > High-Level Constructs to LLVM IR" document is ready for prime time. > Until then, you can review and study it at this URL: > > https://github.com/archfrog/llvm-doc/blob/master/MappingHighLevelConstructsToLLVMIR.rst > > > Please notice

Without ANY intent of offending anybody, I simply don't like C++. I did code in it for some 12 years back from 1990 to 2002, but then I left it behind with a feeling of happiness. The main reason I am _trying_ to make a new language is that I hope to one day come up with something that can help retiring C++. I love C# but that language is yet too slow for many demanding problem domains.

That reminds me: Do the web documents reside in a repository somewhere or should I just grab them using wget? 2012/6/14 Michael Spencer <bigcheesegs at gmail.com> > On Wed, Jun 13, 2012 at 4:02 PM, Mikael Lyngvig <mikael at lyngvig.org> > wrote: > > If nobody else is doing it, I can translate the FAQ into Sphinx as I'd > like > > to begin gradually extending