similar to: [LLVMdev] Linking times

Do you specify CMAKE_BUILD_TYPE if you are using cmake? 2012/05/27 18:21 "Mikael Lyngvig" <mikael at lyngvig.org>: > Hi, > > Just a brief follow-up on my link time issue: It was caused by excessive > trashing; I tried rebuilding on a box with 8 gigs of RAM and observed the > memory load while linking clang.exe: It peaked at 5 gigabytes memory, so > now I've

That reminds me: Do the web documents reside in a repository somewhere or should I just grab them using wget? 2012/6/14 Michael Spencer <bigcheesegs at gmail.com> > On Wed, Jun 13, 2012 at 4:02 PM, Mikael Lyngvig <mikael at lyngvig.org> > wrote: > > If nobody else is doing it, I can translate the FAQ into Sphinx as I'd > like > > to begin gradually extending

On Wed, Jun 13, 2012 at 4:47 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > That reminds me: Do the web documents reside in a repository somewhere or > should I just grab them using wget? The website is at http://llvm.org/viewvc/llvm-project/www/trunk/ . The llvm docs are in llvm/docs. Which actually makes me wonder if the LLVM-project FAQ (in reference to Chandler's post in

The irony of this reply is killing me :) On Wed, Jun 13, 2012 at 7:54 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > You're not alone :) Don't let it bug you. > > I finally decided to install a GMail extension that enables reply-all for > all messages, because I kept forgetting. Perhaps you can find such an > extension or simply enable reply-all by default?

If nobody else is doing it, I can translate the FAQ into Sphinx as I'd like to begin gradually extending it so that it some day becomes more than just bare metal. I figure that extending the FAQ is one way to reduce the "noise" on the various mailing lists. Cheers, Mikael -- -- Love Thy Frog! -------------- next part -------------- An HTML attachment was scrubbed... URL:

2012/5/24 Mikael Lyngvig <mikael at lyngvig.org>: > I know that the documentation says that I am to install GnuWin32 tools, but > I strongly oppose that idea.  We Windows people have our own tools and > practices and I think the LLVM developers should open up to a more > multi-platform approach than the current (Unix then, perhaps maybe, Windows) > approach.  CMake works

Hehe, I intentionally left out the group because I just wanted to cheer you up and let you know that there's more than one "retard" on the list. 2012/6/14 Sean Silva <silvas at purdue.edu> > The irony of this reply is killing me :) > > > On Wed, Jun 13, 2012 at 7:54 PM, Mikael Lyngvig <mikael at lyngvig.org>wrote: > >> You're not alone :)

btw, the "default reply-to-all" extension for gmail works great! On Wed, Jun 13, 2012 at 8:11 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hehe, I intentionally left out the group because I just wanted to cheer > you up and let you know that there's more than one "retard" on the list. > > > 2012/6/14 Sean Silva <silvas at purdue.edu> >

On Jun 13, 2012, at 4:47 PM, Mikael Lyngvig wrote: > 2012/6/14 Michael Spencer <bigcheesegs at gmail.com> > On Wed, Jun 13, 2012 at 4:02 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > > If nobody else is doing it, I can translate the FAQ into Sphinx as I'd like > > to begin gradually extending it so that it some day becomes more than just > > bare

Hi again, The Visual Studio getting started guide ( http://llvm.org/docs/GettingStartedVS.html) mentions the "llvm-lit" tool, but fails to mention these things: 1. Either you need to run it from bash or a similar Unix shell, as Windows does not recognize the extensionless Python script that it is. 2. Alternatively, you can invoke it using Python like this: python bin/llvm-lit

On Wed, Jun 13, 2012 at 4:02 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > If nobody else is doing it, I can translate the FAQ into Sphinx as I'd like > to begin gradually extending it so that it some day becomes more than just > bare metal.  I figure that extending the FAQ is one way to reduce the > "noise" on the various mailing lists. > > > Cheers,

On Wed, Jun 13, 2012 at 4:37 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > I think the best way that I can currently contribute to the project is > through technical writing. So I see myself as doing a serious, long-term > project of extending the FAQ. So, I can affirm that I want to really start > working :) Awesome. I was myself thinking of a number of FAQs: >

Hi, I accidentally noticed the following line when building LLVM and Clang on Windows 7 x64 using Mingw64: Linking CXX shared library ..\..\..\..\bin\liblibclang.dll "Liblib" seems a bit overkill. FYI. BTW, for those who happen to search on LLVM, Clang, Windows, and Mingw64: The v3.1 release does NOT build with Mingw64. I believe this has been fixed in the Subversion sources as

As I read, I'm writing stuff here things come to me: 1. Don't indent the list. Some of the other RST files do this, but it is incorrect since it indents the list! The list is semantically "at the top level" of indentation (it's not a sub-element of anything). 2. don't have that mini "table of contents" list at the beginning. sphinx will generate that itself

Hi, Here's the final, confirmed working version of my Windows guide for how to set up a MinGW buildbot slave. Please consider to include it in the documentation on the LLVM website. Basically, it saves the newcoming Windows user about two or three days of experimentation to get it all working. I think those days are important as many people balk at spending days on figuring out how to get

Okay with the manual versus FAQ strategy. I just have to mention that languages like C++ has many FAQs all over the net, altogether totalling perhaps thousands of questions and I see C++ as simple compared to LLVM. But I have plenty to do now. If nothing else, I could try reading the manuals ;-) 2012/6/14 Chandler Carruth <chandlerc at google.com> > On Wed, Jun 13, 2012 at 4:37 PM,

Hi, My Windows build slave is now up and running. The only thing that isn't set up correctly yet is the test phase. Given this: 1. "make check" works fine on Mingw64/Windows x64. 2. "make clang-test" reports a 29 unexpected failures: Expected Passes : 4617 Expected Failures : 30 Unsupported Tests : 10 Unexpected Failures: 29 And make then fails with

const uint64_t UnknownAddressOrSize <http://llvm.org/doxygen/namespacellvm_1_1object.html#abcfa9b6f24c69c52d2489a102ba3583c> = ~0ULL This found at line 260 in ObjectFile.h. Notice the 0ULL thingy. Cheers, Mikael -- Love Thy Frog! -------------- next part -------------- An HTML attachment was scrubbed... URL:

Mikael, Thanks for working on. My gross comments... - Canonical URL of LLVM project is; http://llvm.org/ , not www.llvm.org. - "test-suite and cygwin" could be split out. It would be special thing. - Memory/storage requirements would be moved to "A.B Debugging". Less memory would be enough without debug build. - Python (x64 binary) is available, too. I am using. Python

Done. Do you want to see it again or should I simply ship it off to llvm-commits? The only thing I've changed from the original HTML is that I've changed a few missing code pieces into using code markup. And now I've made the changes you requested and I think it looks really good: Each question being a subsection of its own works very well in my opinon. Oh, heck, I might as well