Displaying 6 results from an estimated 6 matches for "modulestructure".
Did you mean:
modelstructure
2010 Aug 15
1
[LLVMdev] A few small errors in the language reference guide
Hi,
* The example under http://llvm.org/docs/LangRef.html#modulestructure is missing several line breaks
* The link under "void" at http://llvm.org/docs/LangRef.html#namedtypes goes to an invalid destination
Jonas
2002 Sep 10
0
[LLVMdev] Re: Qustion about LLVM docs (fwd)
I am forwarding a question and response about the use of getelementptr:
> Hi. I found an LLVM code example that might be an error. The relevant
> URL is: http://llvm.cs.uiuc.edu/docs/LangRef.html#modulestructure
>
> There is a piece of code which looks like this:
>
> ; Declare the string constant as a global constant...
> %.LC0 = internal constant [13 x sbyte] c"hello world\0A\00"
>
> Which is then followed by this:
>
> ; Convert [13x sbyte]* to sbyte *...
> %cas...
2006 Jun 13
1
[LLVMdev] JIT'ing constant globals
On Mon, 12 Jun 2006 12:27:36 -0500 (CDT)
Chris Lattner <sabre at nondot.org> wrote:
> On Mon, 12 Jun 2006, Simon Burton wrote:
> > It seems one can only put constant global statements
> > _before_ any functions are defined, not after.
>
> This is true in .ll files, but not necessary in LLVM modules.
Yes, I'm generating .ll files.
I'm using a workaround:
2007 Jun 12
2
[LLVMdev] Problems with the tools
I just built LLVM 2.0 on Windows with Visual C++ 2005. After a few tweaks, it produced several nice .exe files.
I tried to compile a simple Hello-World program as given in the documentation:
--------------------------------------------------------------------------------------
; Declare the string constant as a global constant...
%.LC0 = internal constant [13 x i8 ] c"hello
2003 Nov 16
0
[LLVMdev] Packages
On Sun, 2003-11-16 at 17:13, Chris Lattner wrote:
> > The point here is that XPL needs to keep track of what a given variable
> > represents at the source level. If the compiler sees a map that is
> > initially small it might represent it in LLVM assembly as a vector of
> > pairs. Later on, it gets optimized into being a hash table. In order to
> > do that and keep
2003 Nov 16
3
[LLVMdev] Packages
> The point here is that XPL needs to keep track of what a given variable
> represents at the source level. If the compiler sees a map that is
> initially small it might represent it in LLVM assembly as a vector of
> pairs. Later on, it gets optimized into being a hash table. In order to
> do that and keep track of things, I need to know that the vector of
> pairs is