similar to: [LLVMdev] code generation order

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 file, I'd have to write everything in the order > prescribed by the assembler

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

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

>> >> I think I may have found an exception to this -- the API seems to >> require me to have all the fields for a struct ready before I >> construct the struct. I don't have the ability to make a struct >> type, use it to declare some variables, and still contribute fields >> to it during the rest of the compilation. >> >> Is there a

On Mon, 28 Apr 2008 17:54:31 -0400, Gordon Henriksen wrote: > On Apr 28, 2008, at 17:32, Hendrik Boom wrote: > >> In http://llvm.org/docs/FAQ.html, when taking about writing a compiler >> that uses LLVM (at least I think that's what the FAQ question is >> asking), >> the FAQ recommends >> >>> # Call into the LLVM libraries code using your

On Sat, Sep 13, 2008 at 11:09 AM, Hendrik Boom <hendrik at topoi.pooq.com> wrote: > What I want is to be able to use the fields that have already been > defined, even though the type isn't complete yet. The vector<const > Type*> is all I have at that moment, and it isn't a type. But by the > time I have a type it's frozen and I can't add new fields to it.

On Fri, 12 Sep 2008 11:06:30 -0700, Eli Friedman wrote: > On Fri, Sep 12, 2008 at 9:35 AM, Hendrik Boom <hendrik at topoi.pooq.com> > wrote: >> I'd like to be able to make use of a structure type and its fields >> before it is completely defined. To be specific, let me ask detailed >> questions at various stages in the construction of a recursive type. I

On Thu, 12 Jun 2008 16:05:19 -0400, Gordon Henriksen wrote: > > Partially opaque types can be refined. This section of the programmer's > manual is applicable: > > http://llvm.org/docs/ProgrammersManual.html#BuildRecType > > — Gordon Here it is: : // Create the initial outer struct : PATypeHolder StructTy = OpaqueType::get(); : std::vector<const Type*> Elts; :

There wouldn't happen to be an index telling one which libraries define which symbols, would there? For example, if I'm told alvm.o: In function `llvm::Function::Create(llvm::FunctionType const*, llvm::GlobalValue::LinkageTypes, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, llvm::Module*)':

On Jun 12, 2008, at 13:25, Hendrik Boom wrote: > So it appears that types are processed for identity the moment they > 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

On 2008-04-29, at 08:41, Hendrik Boom wrote: > On Mon, 28 Apr 2008 17:54:31 -0400, Gordon Henriksen wrote: > >> On Apr 28, 2008, at 17:32, Hendrik Boom wrote: >> >>> In http://llvm.org/docs/FAQ.html, when taking about writing a >>> compiler >>> that uses LLVM (at least I think that's what the FAQ question is >>> asking), >>> the

In http://llvm.org/docs/FAQ.html, when taking about writing a compiler that uses LLVM (at least I think that's what the FAQ question is asking), the FAQ recommends > # Call into the LLVM libraries code using your language's FFI (foreign > function interface). > > * for: best tracks changes to the LLVM IR, .ll syntax, and .bc > format > * for:

On Apr 28, 2008, at 17:32, Hendrik Boom wrote: > In http://llvm.org/docs/FAQ.html, when taking about writing a compiler > that uses LLVM (at least I think that's what the FAQ question is > asking), > the FAQ recommends > >> # Call into the LLVM libraries code using your language's FFI >> (foreign >> function interface). >> >> * for:

On Sat, 13 Sep 2008 11:45:50 -0700, Eli Friedman wrote: > On Sat, Sep 13, 2008 at 11:09 AM, Hendrik Boom <hendrik at topoi.pooq.com> > wrote: >> What I want is to be able to use the fields that have already been >> defined, even though the type isn't complete yet. The vector<const >> Type*> is all I have at that moment, and it isn't a type. But by the

I'd like to be able to make use of a structure type and its fields before it is completely defined. To be specific, let me ask detailed questions at various stages in the construction of a recursive type. I copy from http://llvm.org/docs/ProgrammersManual.html#TypeResolve // Create the initial outer struct PATypeHolder StructTy = OpaqueType::get(); Is it possible to declare

Hendrik, You could also just "touch ~/.cvspass" to create the file which should eliminate the warning. However, since you did a login, and it seemed successful, chances are the file now exists (containing the blank password for anon at llvm.org). Reid. On Mon, 2006-08-07 at 09:14 -0500, John Criswell wrote: > Hendrik Boom wrote: > > I tried to access the latest LLVM, since

On Mon, 02 Jun 2008 09:52:16 -0700, Thomas Hudson wrote: > You need to use the script 'llvm-config' to pass correct arguments to g > ++: > > g++ -o broken.o `llvm-config --cxxflags` broken.cpp > > Interesting. When I type the command as you provided it (using cut-and-paste) I get: hendrik at lovesong:~/dv/lang/hlvm$ g++ -o broken.o `llvm-config --cxxflags`

On Mon, 07 Aug 2006 09:26:07 -0700, Reid Spencer wrote: > Hendrik, > > You could also just "touch ~/.cvspass" to create the file which should > eliminate the warning. However, since you did a login, and it seemed > successful, chances are the file now exists (containing the blank > password for anon at llvm.org). Indeed, the file is there. > > Reid. >

I tried to access the latest LLVM, since several messages here so far have referred me to it. Now I have no experience with CVS-over-the-net. My previous experiences with versoin control have been RCS and Monotone. Brief summary: hendrik at lovesong:~/dv$ mkdir llvm hendrik at lovesong:~/dv$ cd llvm hendrik at lovesong:~/dv/llvm$ cvs -d :pserver:anon at llvm.org:/var/cvs/llvm login Logging in

The hardware requirements claim that there is no native code generation for the AMD 64. Is anyone working toward this? -- hendrik