similar to: [LLVMdev] binary release would be great

On Fri, 21 Jan 2005 12:14:41 -0800, Reid Spencer <reid at x10sys.com> wrote: > > Sorry for the sad state of the cygwin build. I had hoped to have it > cleaned up by now but many other things have been taking my time. > Although the build has been succeeding in recent days, I'm not sure it > will buy you anything. NONE of the nightly tests pass on cygwin. <ulp!>

Marshall Spight wrote: >>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 archives somewhere that there are significant >performance issues with the

Hi Marshall, LLVM *is* cool .. just not on cygwin! :) Sorry for the sad state of the cygwin build. I had hoped to have it cleaned up by now but many other things have been taking my time. Although the build has been succeeding in recent days, I'm not sure it will buy you anything. NONE of the nightly tests pass on cygwin. Until I can get some time to figure out why that is happening, I doubt

Hi, I'm looking into LLVM, and I must say it looks supremely cool. However, I'm having a hard time getting anywhere with it, since I don't have a linux machine here, and cygwin seems like a bit of a second-class citizen. The instructions to build the cygwin binaries are outdated, so I have to just make some guesses as to what the right thing to do is, and I'm apparently not

Hi, What's the state of llvm on various platforms? I've tried working with it on windows/cygwin a few times, and been fairly frustrated. I made some abortive efforts on RedHat 9, which also didn't go so well, but I put much less time into them. Is there a plan or a timeline to end up with some low-intensity linux target? Sort of like: grab these three RPMs and go. Having to get my

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 docs myself ... doxygen simply refuses to create pages for classes

>> In other words, abandoning overflow detection makes the >> duplication of types redundant, while requiring it would be a >> great burden on CPUs that don't have overflow exception hardware. > >Yes, you're right. This has been a desired change for quite some time >now. Unfortunately, its a huge impact to nearly every part of LLVM. We >will

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 have been

>>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 ?

Chris Lattner wrote: >> I tried generating the docs myself ... doxygen simply refuses to >> create pages for classes defined in anonymous namespaces in cpp files. >> I enabled options such as EXTRACT_ALL, EXTRACT_PRIVATE and >> EXTRACT_LOCAL, but no luck. How is the publicly available >> documentation generated? > > They are generated from the Makefile in

Chris Lattner wrote: > As such, I'd like to open up a forum for naming ideas. I think we need to > continue to use the name 'LLVM' to refer to the IR (i.e. that which 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

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

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

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.

Yeah, cygwin is a bit of a beast. There's no pre-compiled binary available (I'm working on it). If you want to build yourself, follow the instructions in the CFEBuildInstr.html 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

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 sizes that are not target dependent. A ulong is

shding at mtu.edu wrote: > Hi, > Where can I find the main function of llvm compiler in the source file? > Thanks! Well, there's a loaded question. :) It depends on "which" compiler you mean. If you're talking about the llvm-gcc and llvm-g++ compilers (C/C++ to LLVM) then they are in the downloadable tarballs available here: http://llvm.cs.uiuc.edu/releases/. You

Hello, I've got a handful of i386 boxes, and a handful of amd64 boxes running a 32-bit application, the reasons for this exact configuration mystify me as well as the deployment predates my time in the environment. Now that the dataset the application is loading is rapidly approaching 512MB we're starting to tweak kern.maxdsiz and kern.dfldsiz to 1GB. The i386 boxes are doing

On Tue, Aug 6, 2019 at 1:51 PM Kuehling, Felix <Felix.Kuehling at amd.com> wrote: > > On 2019-08-06 13:44, Jason Gunthorpe wrote: > > On Tue, Aug 06, 2019 at 07:05:53PM +0300, Christoph Hellwig wrote: > >> The option is just used to select HMM mirror support and has a very > >> confusing help text. Just pull in the HMM mirror code by default > >>