From c9666381f6493ee760f7dfcdff24c4fad79dc591 Mon Sep 17 00:00:00 2001 From: Vincent Esche Date: Thu, 13 Dec 2018 14:17:18 +0100 Subject: [PATCH] =?UTF-8?q?Fixed=20links=20in=20`=E2=80=A6/docs/compare-ll?= =?UTF-8?q?vm.rst`?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- cranelift/docs/compare-llvm.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cranelift/docs/compare-llvm.rst b/cranelift/docs/compare-llvm.rst index e23f9f7890..ad0e71eaf4 100644 --- a/cranelift/docs/compare-llvm.rst +++ b/cranelift/docs/compare-llvm.rst @@ -109,7 +109,7 @@ low-level optimizations are sufficient. And, it removes some constraints in the mid-level optimize IR design space, making it more feasible to consider ideas such as using a -[VSDG-based IR](https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-705.pdf). +`VSDG-based IR `_. Program structure ----------------- @@ -118,7 +118,7 @@ In LLVM IR, the largest representable unit is the *module* which corresponds more or less to a C translation unit. It is a collection of functions and global variables that may contain references to external symbols too. -In `Cranelift's IR` `_, +In `Cranelift's IR `_, used by the `cranelift-codegen `_ crate, functions are self-contained, allowing them to be compiled independently. At this level, there is no explicit module that contains the functions.