Lines Matching refs:code
12 Can I modify LLVM source code and redistribute the modified source?
19 Can I modify the LLVM source code and redistribute binaries or other tools based on it, without red…
34 How portable is the LLVM source code?
36 The LLVM source code should be portable to most modern Unix-like operating
38 Most of the code is written in standard C++ with operating system
47 what's going on. Basically, in code like:
49 .. code-block:: llvm
80 … compiler. How should I interface with the LLVM middle-end optimizers and back-end code generators?
87 1. **Call into the LLVM libraries code using your language's FFI (foreign
97 * *against:* lots of ugly glue code to write
120 most common hurdle with calling C from managed code is interfacing with the
127 which is useful for code representation but will not support the high level
140 Can I compile C or C++ code to platform-independent LLVM bitcode?
143 example of this is the preprocessor. A very common way that C code is made
144 portable is by using the preprocessor to include platform-specific code. In
158 Questions about code generated by the demo page
174 before they could possibly be used in the file. The code that you see in the
175 ``.ll`` file corresponds to the constructor and destructor registration code.
177 If you would like to make it easier to *understand* the LLVM code generated
182 Where did all of my code go??
185 all of the code that you typed in. Remember that the demo script is running
186 the code through the LLVM optimizers, so if your code doesn't actually do
189 To prevent this, make sure that the code is actually needed. For example, if
195 What is this "``undef``" thing that shows up in my code?
201 .. code-block:: c
214 example, this code:
216 .. code-block:: llvm
228 .. code-block:: llvm
238 "all their code disappears". Setting the calling convention on the caller and
242 The answer is that this code has undefined behavior, but it is not illegal.
244 this would have to ensure that it doesn't, and there is valid code that can
245 create this sort of construct (in dead code). The sorts of things that can
249 .. code-block:: llvm
271 code is perfectly well defined). If you run this through the inliner, you
272 get this (the explicit "or" is there so that the inliner doesn't dead code
275 .. code-block:: llvm
295 have to know about this sort of thing, so it needs to be valid code. In this
296 case, dead code elimination can trivially remove the undefined code. However,
299 .. code-block:: llvm
318 code to be well-defined, but no amount of dead code elimination will be able
325 .. code-block:: llvm