similar to: [LLVMdev] Clang/Clang++ standard headers?

On Mon, May 28, 2012 at 07:42:12PM +0200, Mikael Lyngvig wrote: > Does Clang/Clang++ not have its own set of standard headers? Isn't this a > serious issue if Clang/Clang++ is ever to outdo GCC/G++? Is there any work > in progress on this? It provides the compiler-centric headers. It doesn't replace the rest of the C runtime library. That wouldn't make much sense. Joerg

Hi again again, I'm trying to build my compiler frontend in C++ on Windows 7 x64 using clang++.exe. I want to use clang++ for my project so that I get a feel for how mature and usable the Windows support is as I gradually get up to speed with LLVM for Windows. I could develop on Linux, but I need the Windows support so I figure I might as well do it the hard way. My code is fairly simple

Thanks for the quick reply. I had a feeling that it was due to missing Windows support in clang++ and LLVM. """ This is due to clang not understanding force_inline. These functions are defined in a header included from Windows.h, so it ends up getting a definition everywhere it is included. """ How much work would it take to add support for force_inline? Are there

On Wed, May 23, 2012 at 4:38 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi again again, > > I'm trying to build my compiler frontend in C++ on Windows 7 x64 using > clang++.exe.  I want to use clang++ for my project so that I get a feel for > how mature and usable the Windows support is as I gradually get up to speed > with LLVM for Windows.  I could develop on

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

Hi Dmitri, I am not using any kind of cache (didn't even know of ccache). I have now installed ccache. Perhaps ccache should be mentioned in the buildbot document so that every buildbot owner knows about it? It is currently running Arch Linux ARM. if there are good reasons to switch to something else, I'll be happy to do that, although I am generally very happy about Arch Linux.

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

On Wed, Nov 13, 2013 at 5:28 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Dmitri, > > I am not using any kind of cache (didn't even know of ccache). I have now > installed ccache. Perhaps ccache should be mentioned in the buildbot > document so that every buildbot owner knows about it? Possibly. > It is currently running Arch Linux ARM. if there are good

Oh, didn't realize that there already is a semi-official build of CMake with Ninja support. I am trying it out right now and it seems very promising. So I'll change the document to use Ninja instead of "MinGW Makefiles". No need to waste energy on MinGW and MSYS Makefiles when Ninja outdoes them both. I thought people would have to build CMake themselves, something I'd

Hi, [Synopsis: Mikael thinks Windows support is overlooked and that this is a strategic error. You can skip to the next mail now, if you'd like :-) Long, long, long mail follows.] Before I go on, I'd like to informally apologize for my many postings to this mailing list. I have no intentions of spamming it, but I still feel a need to grasp certain things that seem to be implied by the

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

Hi, I was thinking about the potential for link-time optimizations. And the fact that you already now output LLVM bitcode to object files, archives, and perhaps even executables (that would give a .NET flavor to LLVM, I wonder if this can be made to work seamlessly on Windows [1]). Then I thought about the fact that you seem intent on supporting all native formats that you run into. I was then

Mikael Lyngvig <mikael at lyngvig.org> writes: [snip] > Yes, I am quite familiar with the CMake documentation, but why are you > asking? That's not the cmake documentation, that's the LLVM cmake documentation: a short document that tries to explain everything you need to know about cmake to build LLVM. I had the impression that you were duplicating a large chunk of the info

Hi, I just did a "make install" on Win7x64 using Mingw64 and it dropped off the files in "C:\Program Files (x86)\LLVM". That's almost right, but nicer would be if the 64-bit build was dropped off in "C:\Program Files\LLVM". I am fairly confident that it is me who is doing something wrong because I simply do this: (retrieve trunk version of LLVM, Clang,

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:

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

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 :)

A quick question while I am adding a tiny section on ccache to the HowToAddABuilder document: Why do you set CCACHE_CPP2 to yes? From reading the manual, I get the impression that this is much slower than the default and that it should only be used with tricky compilers or when debugging. Is Clang such a tricky compiler? If so, I suppose Clang should be fixed, not the ccache configuration. --