similar to: [LLVMdev] [PATCH] docs/tutorial/ Kaleidoscope typos

Applied in r106468, thanks! -Chris On Jun 2, 2010, at 5:23 PM, Adam Warner wrote: > Index: docs/tutorial/LangImpl6.html > =================================================================== > --- docs/tutorial/LangImpl6.html (revision 105365) > +++ docs/tutorial/LangImpl6.html (working copy) > @@ -531,7 +531,7 @@ > def unary-(v) > 0-v; > > -# Define > with

On Mon, 21 Jun 2010 15:31:57 -0500, Chris Lattner <clattner at apple.com> wrote: > Applied in r106468, thanks! > > -Chris I think there's a few bugs left in the Kaleidoscope tutorial -- I noticed somebody converted some of the "Builder.CreateAdd" to CreateFAdd, etc., but there seem to be a few that got missed. Attached diff is what I could find... Kevin Kelley

Hi all, I'm currently in the process of updating the Kaleidoscope tutorials (first and foremost, the ORC/BuildingAJIT ones), and I've noticed a fair few 404s which are lingering within the current visible documentation. Some of these don't seem to have linked to existing pages for a while. I was wondering if there was a way to set up a check in the buildbot to ensure that

Patrick, how long does the crawl take? I suspect if we fixed internal documentation links so that they point to local copies of documentation when building locally it would be quite quick (no actual idea though). That in turn would probably make it feasible to add to the existing documentation build bots, I think. James On Thu, 29 Aug 2019 at 03:47, Neil Nelson via llvm-dev < llvm-dev at

Upon writing my register allocation algorithm, I am concerned that a load may be skipped due to a branch. For instance consider the psudocode int x = 1 ... if( false ) load x y = 3*x else y = 4*x ... The load happens in the false block because this is when the variable is first seen. The load is not preformed in the else block because the register allocator may see it loaded already. Do

Hi Chris, Here are some diffs for the final three chapters of the Kaleidoscope tutorial. The changes are the same sort of changes as previous diffs. One question though....under the "Memory in LLVM" section of chapter 7 (mutable variables) there is a statement like this: The mem2reg pass implements the standard "iterated dominator frontier" algorithm... Should this read

On Nov 11, 2007, at 2:41 PM, Kelly Wilson wrote: > Hey Chris: > > Here are the diffs for the next few chapters of the tutorial that I > have > edited. Nice! You are an excellent editor, I'm impressed. I committed these without any changes here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20071112/055566.html Thank you for the help with this. > Please

s/ =/ = Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com> --- daemon/btrfs.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index 8b5779a..306cade 100644 --- a/daemon/btrfs.c +++ b/daemon/btrfs.c @@ -512,7 +512,7 @@ do_btrfs_subvolume_list (const mountable_t *fs) goto error; } - struct

From: Yuan Liu <liuyuan at google.com> Fix a warning thrown from virtio_mmio_remove(): Device 'virtio0' does not have a release() function The fix is according to virtio_pci_probe() of drivers/virtio/virtio_pci_common.c Signed-off-by: Yuan Liu <liuyuan at google.com> --- drivers/virtio/virtio_mmio.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

From: Yuan Liu <liuyuan at google.com> Fix a warning thrown from virtio_mmio_remove(): Device 'virtio0' does not have a release() function The fix is according to virtio_pci_probe() of drivers/virtio/virtio_pci_common.c Signed-off-by: Yuan Liu <liuyuan at google.com> --- drivers/virtio/virtio_mmio.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

I think not. In virtio_pci_common, vp_dev is allocated by kzalloc so a kfree is needed. Here vm_dev is allocated by devm_kmalloc which is "automatically freed on driver detach" from the comment (drivers/base/devres.c:769). On Thu, Nov 24, 2016 at 6:37 PM, Jason Wang <jasowang at redhat.com> wrote: > > > On 2016?11?24? 08:31, Yuan Liu wrote: > >> From: Yuan Liu

I think not. In virtio_pci_common, vp_dev is allocated by kzalloc so a kfree is needed. Here vm_dev is allocated by devm_kmalloc which is "automatically freed on driver detach" from the comment (drivers/base/devres.c:769). On Thu, Nov 24, 2016 at 6:37 PM, Jason Wang <jasowang at redhat.com> wrote: > > > On 2016?11?24? 08:31, Yuan Liu wrote: > >> From: Yuan Liu

The link to the next chapter in the navigation list at the top of this page of the OCaml Kaleidoscope tutorial goes to the C++ version: http://llvm.org/docs/tutorial/OCamlLangImpl3.html. The link to chapter 8 in the first chapter is broken: http://llvm.org/docs/tutorial/OCamlLangImpl1.html#intro. It links to the unvavailable page http://llvm.org/docs/tutorial/OCamlLangImpl8.html. I think it

Hi Folks, I am just starting to get familiar with the llvm framework, thank you at first for this nice tool which seems really powerful! I have studied so far the Kaleidoscope example and other docs at llvm.org and try to figure out which would be the "right" way (well I suppose there are many) to integrate the framework into my compiler project, but there is still quite a gap between

Link with -rdynamic or provide a mapping. /Stein Roger Andrii Vasyliev wrote: > Hi > > I hope this is a proper place to put my question. > > I've compiled Kaleidoscope from "Adding JIT and Optimizer Support" tutorial. > Basically it works just fine but when I try to run extern'ed putchard > function it aborts. > Please, tell me what am I doing wrong?

Thanks, -rdynamic helps! It's a pity that it's not written in the tutorial. Also I'm interested how can I provide a mapping? 2008/9/25 srs <skaflotten at gmail.com>: > Link with -rdynamic or provide a mapping.

I've already filed a bug report but nobody cares :-( Is it possible to fix the documentation? Because I think the tutorial is really important to beginners, which should not be misleading. -- Haohui On Sep 25, 2008, at 9:42 AM, Andrii Vasyliev wrote: > Thanks, -rdynamic helps! It's a pity that it's not written in the > tutorial. > > Also I'm interested how can I

Haohui Mai <haohui.mai at gmail.com> writes: > I've already filed a bug report but nobody cares :-( > > Is it possible to fix the documentation? Because I think the tutorial > is really important to beginners, which should not be misleading. > >> Thanks, -rdynamic helps! It's a pity that it's not written in the >> tutorial. >> >> Also

Hi all, being myself still a llvm novice I thought I'd do all fellow newbies a favor and provide a patch that makes the code in the tutorial compile with 2.4, just to avoid extra headache in the (not so easy) process of getting into the matters... it's actually just the new template parameters of the IRBuilder class. The patch is on the docs/ level since I didn't checkout the whole

Thank you very much for your idea, chuck Zhao. May I ask whether you have solved this problem or not? -- Best regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20081203/f53425e5/attachment.html>