search for: poimter

Displaying 4 results from an estimated 4 matches for "poimter".

Did you mean: gpointer
2008 Jun 12
2
[LLVMdev] code generation order revisited.
...ocessed for identity the moment they are made during parse tree construction? This means that a type has to be completely known on creation. Presumably there's some mechanism tor a type that isn't completely known yet -- or is thet avoided by having a type 'pointer' instead of 'poimter-to-foo'? -- hendrik
2008 Jun 12
0
[LLVMdev] code generation order revisited.
...are made during parse tree construction? Yes. > This means that a type has to be completely known on creation. Yes. > Presumably there's some mechanism tor a type that isn't completely > known yet -- or is thet avoided by having a type 'pointer' instead > of 'poimter-to-foo'? Partially opaque types can be refined. This section of the programmer's manual is applicable: http://llvm.org/docs/ProgrammersManual.html#BuildRecType — Gordon
2008 Jun 12
0
[LLVMdev] code generation order revisited.
On Jun 12, 2008, at 11:38, Hendrik Boom wrote: > On Tue, 06 May 2008 16:06:35 -0400, Gordon Henriksen wrote: > >> On 2008-05-06, at 13:42, Hendrik Boom wrote: >> >>> One more question. I hope you're not getting tired of me already. >>> Does generating LLVM code have to proceed in any particular order? >>> >>> Of course, if I am writing
2008 Jun 12
2
[LLVMdev] code generation order revisited.
On Tue, 06 May 2008 16:06:35 -0400, Gordon Henriksen wrote: > On 2008-05-06, at 13:42, Hendrik Boom wrote: > >> One more question. I hope you're not getting tired of me already. Does >> generating LLVM code have to proceed in any particular order? >> >> Of course, if I am writing LLVM assembler by appending characters to >> the >> end of a sequential