search for: illuvium

Hi, The docs available on illuvium.com are different from the one's present in the doxygen tarball on the same page ... can the tarball be generated from the same docs as the browseable version? I considered crawling the illuvium.com site, but it would be better to simply have a tarball available. I tried generating the doc...

On Tue, 15 Nov 2005, Sameer D. Sahasrabuddhe wrote: > The docs available on illuvium.com are different from the one's present in > the doxygen tarball on the same page ... can the tarball be generated from > the same docs as the browseable version? I considered crawling the > illuvium.com site, but it would be better to simply have a tarball available. Agreed. I h...

Hi LLVMers, I've been doing a little work on the mirror site. It now has a new domain name: iLLuViuM.net. Don't ask about the name :) I've fixed the doxygen documentation build and it is current as of now. It hadn't been current since October! Someone should tell me about these things :) There are also new direct links into the command guide and general documentation. For now, llvm...

...Makefile in the llvm/docs directory, which > has a doxygen.cfg in it. I used the same file ... the problem is that doxygen is not producing documentation for classes inside anonymous namespaces ... I tried the options mentioned above, but didn't work. For example, consider this: http://illuvium.com/docs/doxygen/classSteens.html This was generated from lib/Analysis/DataStructure/Steensgaard.cpp, but when I tried that on my setup, no such file is created: sameerds at trantor5:~/data/llvm-1.6$ find docs/doxygen -name "*Steen*" docs/doxygen/html/Steensgaard_8cpp-source.html docs/...

You know what I would really love? I set of pre-built llvm binaries. Either for Windows or RedHat. IIUC, the cygwin nightly build hasn't succeeded since March, and the latest download on illuvium.net predates that. I'd love to be able to try out 1.6, but having to build my own compiler to build it is a substantial barrier. I know there are binaries for the gcc frontend, which is cool, but I'd most like to be able just to get one whole big package with binaries for everything. It doe...

...is > described in http://llvm.org/docs/LangRef.html), and we should plan to > attach LLVM as a suffix to the project name for several years to come: For > example: "Use the Foo/LLVM Compiler System, it runs infinite loops faster > than the competition!". > How about Illuvium? It's pronounceable, it pays homage to "LLVM", and the domain's already taken by someone who might be persuaded to give it up :)

>>Does anyone know a source for a pre-built version of the same? > >To my knowledge there is no pre-built version of the cfe. See following link for CFE :- http://illuvium.com/download/ It maybe a bit out of date. I believe the CFE maybe broken at the moment, at least the Cygwin nightly test reports that it is broken and I believe this is the same thing ? http://illuvium.com/testresults/Cygwin/ > However, if you like I can give you the build instructi...

Hi Reid, Reid Spencer wrote: > Yes, for that you need TargetData: > > http://illuvium.net/docs/doxygen/classllvm_1_1TargetData.html I feared that that would be the answer :-). We're not using the LLVM-API at the moment. We're just generating a .ll file 'by hand', e.g. via simple string operations. I guess we get what we deserve :-). Thanks for your help, Carl Fr...

The llvm.cs.uiuc.edu site does not seem to be updating at the moment so it contains the old instructions. If you're looking for the new instructions on the Projects.html page, you can view them here: http://illuvium.net/docs/Projects.html Reid. On Sat, 2005-01-15 at 18:30, Reid Spencer wrote: > The proposed makefile changes have been committed. If you are working > from CVS head and you use the LLVM Makefile System in your own project, > please make a note of the following: > > 1. If your m...

...l document carefully, especially noting the Cygwin specific stuff. For example, you can't use the default gcc that comes with Cygwin. I've been successful with GCC 3.4.3 on Cygwin. I've uploaded a zipped tar file my Cygwin CFE "install" directory. You can get it here: http://illuvium.com/download/ Use at your own risk (i.e. it works for me, but your mileage may vary). Reid. On Thu, 2005-02-24 at 14:21, Aaron Gray wrote: > There do not seem to be any binaries for CygWin only Linux and the Mac :( > > I tried building the frontend on CygWin but ended up with a makein...

I'm building on cygwin. But the procedure for building the front-end on Cygwin is a bit daunting, to say the least,. Does anyone know a source for a pre-built version of the same?

>From: "Robin Davies" <rerdavies at rogers.com> > >I'm building on cygwin. But the procedure for building the front-end on >Cygwin is a bit daunting, to say the least,. > >Does anyone know a source for a pre-built version of the same? > To my knowledge there is no pre-built version of the cfe. However, if you like I can give you the build instructions.

Hi Reid, On Mon, Jun 20, 2005 at 07:08 -0700, Reid Spencer wrote: > The thing you're missing is that LLVM's primitive types have well known, > fixed sizes that are not target dependent. A ulong is 8 bytes. A uint is > 4 bytes. A ushort is 2 bytes. Etc. and always. Don't aligning rules make it hard to compute the size of a whole struct from the sizes of it's members?

Yes, for that you need TargetData: http://illuvium.net/docs/doxygen/classllvm_1_1TargetData.html Reid. On Mon, 2005-06-20 at 17:08 +0200, holger krekel wrote: > Hi Reid, > > On Mon, Jun 20, 2005 at 07:08 -0700, Reid Spencer wrote: > > The thing you're missing is that LLVM's primitive types have well known, > > fixed...

...e back later to the task of targetting llvm. > I'll be looking at this in the coming weeks. Cygwin build support is > scheduled for LLVM 1.5 (March). When I get binaries that pass the > nightly test, I'll make them available on my download page. You can > reach that at http://illuvium.net/ Thanks. That would be cool. > FYI, work progresses on the Win32 native port which you might also find > interesting. It might even get done before the cygwin stuff. Jeff Cohen > is working on that. Perhaps he can indicate the status of that effort. I recall reading on the llvm ar...

...c.edu/releases/. You can also get them via CVS using the llvm-gcc repository name. If you're talking about the llc compiler (LLVM to machine code), it is in the llvm repository under tools/llc, however most of the code consists of the various libraries that make up LLVM (viewable at http://illuvium.com/cgi-bin/cvsweb.cgi/llvm/lib/), in particular the assembler (lib/AsmParser), Bytecode facilities (lib/Bytecode), code generation code (lib/Codegen), and target-specific translators (lib/Target). If you're talking about the generic compiler, llvmc, you can find it at the tools/llvmc direc...

Hi, Where can I find the main function of llvm compiler in the source file? Thanks! -- Shuhan

...ot use cygwin in the slightest. It's built with Microsoft Visual Studio. If you have that, it's trivial to build (double click the solution then run "build solution"), but it does require that you have bison, sed, and flex on your machine. Prebuilt binaries are available on illuvium.net. It's usable so long as you are writing your own front end. There are serious technical issues standing in the way of getting llvm-gcc built natively on Windows. Also, only the JIT or interpreter is usable at this time. I haven't gotten around to getting assembler output yet that...

...get > them via CVS using the llvm-gcc repository name. > > If you're talking about the llc compiler (LLVM to machine code), it is in > the > llvm repository under tools/llc, however most of the code consists of the > various libraries that make up LLVM (viewable at > http://illuvium.com/cgi-bin/cvsweb.cgi/llvm/lib/), in particular the > assembler > (lib/AsmParser), Bytecode facilities (lib/Bytecode), code generation code > (lib/Codegen), and target-specific translators (lib/Target). > > If you're talking about the generic compiler, llvmc, you can find it at...

...please make a note of the following: 1. If your makefiles use any BUILD_* variables, they now need to be prefixed with PROJ_ instead of BUILD_. For example, BUILD_SRC_ROOT is now PROJ_SRC_ROOT. 2. There are additional requirements for projects. Please review this file: http://illuvium.net/src/projects/sample/Makefile.common.in as it contains the complete list of variables you need to set and provides some documentation on them. Note that there are three new project related variables you need to set: PROJECT_NAME, PROJ_VERSION, and PROJ_INSTALL_DIR. These varia...