search for: mappinghighlevelconstructstollvmir

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 to give me any feedback, comments, and criticism that you may have to share. Once the document has been finalized and comitted to LLVM, I'll delete the repository at Github - or, pe...

...hing is that I do a lot of small commits with an occasional large commit here and there, and I wouldn't want to provoke a review whenever I change a single line here or there. The reason I use GitHub is that it provides a nifty, colorized page ( https://github.com/archfrog/llvm-doc/blob/master/MappingHighLevelConstructsToLLVMIR.rst) that people (including myself) can view without going through the trouble of installing and running Sphinx locally. And also, it allows people to submit reviews by forking, creating an issue, or attaching a comment (all three of which have already been in use). I think it is better that I do...

...lot of small commits with an occasional large commit > here and there, and I wouldn't want to provoke a review whenever I change a > single line here or there. The reason I use GitHub is that it provides a > nifty, colorized page ( > https://github.com/archfrog/llvm-doc/blob/master/MappingHighLevelConstructsToLLVMIR.rst) > that people (including myself) can view without going through the trouble > of installing and running Sphinx locally. And also, it allows people to > submit reviews by forking, creating an issue, or attaching a comment (all > three of which have already been in use). I think it...

...ig.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: > > 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 to give me any feedback, comments, and criticism that you may have to share. > This looks really awesome! Great idea starting this, and thank you for pushing it fo...

...t to the LLVM-commits list earlier today, but David Blaikie pointed out that the document should be in a state where it can be published before committing it, so that's what I am working on now. For the time being, the document can be found at: https://github.com/archfrog/llvm-doc/blob/master/MappingHighLevelConstructsToLLVMIR.rst As soon as it is ready to be published, it will be moved to the llvm/docs folder. -- Mikael -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131217/c9f5cbaa/attachment.html>

...>> 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 to give me any feedback, comments, and >> criticism that you may have to share. >> >> Once the document has been finalized and comitte...

...; 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 that I specifically do not advocate reviewing the document > for a week or two. But feel free to give me any feedback, comments, and > criticism that you may have to share. > > Once the document has been finalized and comitted to LLVM, I'll delete t...

...bably 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 to give me any feedback, comments, and >>> criticism that you may have to share. >>> >>> Once the document ha...

...ngvig 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 that I specifically do not advocate reviewing the > document for a week or two. But feel free to give me any feedback, > comments, and criticism that you may have to share. > > Once the document has been finalized and comitted to LLVM, I'll delete...

...gt;> 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 to give me any feedback, comments, and >> criticism that you may have to share. >> >> Once the document has been finalized and comitte...

...ably 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 to give me any feedback, comments, and >>> criticism that you may have to share. >>> >>> Once the document ha...

Thanks, I hadn't heard about PNaCl, it's very interesting. I'm currently swimming in http://llvm.org/docs/ trying to learn more about LLVM-IR... Selon JF Bastien <jfb at google.com>: > We (PNaCl team) are in the process of removing older documentation, > this is probably more accurate: > https://developers.google.com/native-client/dev/ > > On Tue, Dec 17,

We (PNaCl team) are in the process of removing older documentation, this is probably more accurate: https://developers.google.com/native-client/dev/ On Tue, Dec 17, 2013 at 6:50 AM, Sam Parker <S.Parker3 at lboro.ac.uk> wrote: > Check out PNaCL > http://www.chromium.org/nativeclient/pnacl > > Cheers, > Sam > > Sam Parker > Research Student > Electronic Systems

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

...its very early infancy. Cheers, Mikael -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131123/616033e8/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: MappingHighLevelConstructsToLLVMIR.rst Type: application/octet-stream Size: 7010 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131123/616033e8/attachment.obj>

...empted insult seen on slashdot > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131125/bceb55bf/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: MappingHighLevelConstructsToLLVMIR.rst Type: application/octet-stream Size: 39013 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131125/bceb55bf/attachment.obj>

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