similar to: [LLVMdev] x86: inline an LLVM IR function?

You should use "opt" with -inline, or -O2/3 to optimise this. llc only runs backend optimisations. On 1 December 2013 18:51, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Sorry for what may possibly be a rather stupid question, but how on earth > do you make LLC inline a function? I've got this code: > > attributes 0 = { alwaysinline nounwind } > >

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

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

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

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

This sounds right to me. If there is no objection, I will implement a patch to enforce this in langref and IR verifier. -----Original Message----- From: Friedman, Eli [mailto:efriedma at codeaurora.org] Sent: Tuesday, September 25, 2018 3:07 PM To: Pan, Wei <wei.pan at intel.com>; Reid Kleckner <rnk at google.com> Cc: llvm-dev <llvm-dev at lists.llvm.org> Subject: Re:

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

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

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

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

We should make LLD to be able to build with GCC even if GCC is a bit buggy. So you wrote that it's no longer build because of the recent change of makeArrayRef removal? I think it's my change (r196475). Can you confirm that you can build if you revert that change? If it has caused the build with GCC to break, we should roll it back. On Sun, Dec 8, 2013 at 3:45 PM, Mikael Lyngvig

On Wed, Nov 20, 2013 at 6:11 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Renato, > > My XU is on build 141 and there hasn't been a single problem yet. No > reboots, no crashes, and as far as I have observed no core dropouts (after > I did the cpu-freq trick you sent me). Perhaps I have a stable board or > perhaps it is because of its revision (rev. 0.3)?

On Wed, Jun 13, 2012 at 4:47 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > That reminds me: Do the web documents reside in a repository somewhere or > should I just grab them using wget? The website is at http://llvm.org/viewvc/llvm-project/www/trunk/ . The llvm docs are in llvm/docs. Which actually makes me wonder if the LLVM-project FAQ (in reference to Chandler's post in

It wouldn't take me more than an hour or two to do the format conversion. It is rather trivial, actually. Just say the word and I'm on to it like a starving bee. I guess I should get used to using the Sphinx layout; I'm simply more familiar with the format I use on my own websites. Have you guys ever considered making a less formal wiki for LLVM documentation - a place where tiny

On Sun, Nov 17, 2013 at 5:17 AM, Sean Silva <chisophugis at gmail.com> wrote: > > > > On Sun, Nov 17, 2013 at 3:50 AM, Mikael Lyngvig <mikael at lyngvig.org>wrote: > >> It wouldn't take me more than an hour or two to do the format conversion. >> It is rather trivial, actually. Just say the word and I'm on to it like a >> starving bee. I

On 3 December 2013 16:08, Mikael Lyngvig <mikael at lyngvig.org> wrote: > You need to get the LLVM Sphinx docs using SVN or Git. If you want it, I > can do the changes for you since I have already everything in place. I think the changes he wants actually are in static html pages, at http://llvm.org/svn/llvm-project/www/trunk. Cheers. Tim.

On Sat, Nov 16, 2013 at 9:15 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > http://llvm.lyngvig.org/Articles/How-to-Setup-an-Arch-Linux-Buildbot-for-LLVM > Notice: You only need Ninja for the test build; none of the official LLVM builders use Ninja as far as I know. My buildbots use ninja. > Please notice that you must specify the absolute path to ninja, otherwise CMake

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 this stuff myself to be able to continue on my own language project. 2. I feel that this needs to

Am I the only one who thinks that it is impractical that the Sphinx intro is buried deep within the lld documentation? I suggest moving it to the Programming Documentation document. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120616/2cb7356d/attachment.html>

Whoops... Seems I forgot the asterisk (*) after the cast. Or something. Because I did insert the cast and it didn't work. But NOW it works. Thank you for spending some time on this - and also for presenting the solution. -- Mikael 2013/12/4 Eli Bendersky <eliben at google.com> > This code: > > declare i32 @printf(i8* nocapture readonly, ...) nounwind > > define