Hi, This may be a daft question, but I have just begun taking a serious look at LLVM for a project that I am working on. Knowing myself pretty well, the probability that I ever complete the project is infinitesimal. I am saying this so you don't jump up out of your chair, yelling "HOORAY!" because I am considering to use LLVM. Think of me as an academic student with too much time on his hands, who is considering if he dares embark on the adventure of getting to know LLVM. The way I see it, my life is going to be much easier if I can delegate the responsibility for generating good code for a number of targets to you guys and instead focus on what I am trying to do. Also, I particularly like the aspect of global optimizations (link-time optimizations) in LLVM - they're one of the selling features of my project. The project is a new programming language (http://www.braceless.org) for which I have been contemplating writing my own backends, but the more I think of it, the less I like the idea. I know you guys from earlier where I posted a suggestion for an alternate implementation of exceptions (one that uses only a single bit to indicate whether an exception has occured and then uses the ordinary return value registers for the pointer to the exception instance, in the rare event that an exception really happens) and it seems to me that there's a natural match between what you do and what I'd like to do. Now I at least have two problems: 1) I've written my "compiler" (language parser, really) in C# and 2) I don't seem to be able to find any procedures on building LLVM on Windows. The first problem is easy to solve; I'll gladly recode my project in C++ just to get to use LLVM. The other problem is a bit bigger, though: LLVM's Windows support. Do you plan to offer "true" Windows support - i.e. release binaries/libraries for Windows and offer a build system that can be used on Windows? Or is LLVM always going to be a mostly *nix-only project? IF LLVM already supports building on Windows, please don't flame me but simply tell me in nice words that I am a moron and how to build LLVM for Windows. I am mostly interested in native x86_64 support for Windows. If there's anything I can do to help, please don't hesitate to let me know. I am on and off coding on portable build system written in C# for .NET/Mono (portable to a wide variety of hosts), which I could perhaps some day finish up and use to build the Windows release of LLVM. Perhaps I can be of some value as a real-life tester of the Win64 backend? My initial goal is to target Windows x64 first and then later on Windows x86, PPC, and so on. P.S. I have a Windows 7 x64 box and a Debian 6.0 Linux 64-bit PPC box (an ancient iMac G5 converted to a Linux box). I do know Linux and CAN work under Linux, but I prefer to use Windows because of the popularity of this platform and the fact that I have spent the last 20+ years working primarily on the PC/Windows platform. P.P.S. I love writing documentation so I wouldn't mind putting together some docs on how to get flying with LLVM on Windows. Sincerely, Mikael Lyngvig -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110220/908fb8a9/attachment.html>
I'm actively working on Windows with LLVM/clang (not directly contributing yet). First of all, it does compile on Windows (only tested in Visual Studio 2010). But, there are still many problems: (1) x86-64 won't compile as far as I know. CMake generates 64-bit soultion, but one project is missing. But, 32-bit solution compiles safely. (2) Although safe compiliation, there are many broken/unimplemented features as of now. I can't detail everything. Some of them are very serious. Currently, LLVM/clang on Windows is very experimental. I'm managed to make it work. I believe the future of LLVM/clang on Windows is very promising. I'm trying to report many bugs as much as I can, and also wish to contribute Windows support! On Sun, Feb 20, 2011 at 1:03 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote:> Hi, > > This may be a daft question, but I have just begun taking a serious look at > LLVM for a project that I am working on. Knowing myself pretty well, the > probability that I ever complete the project is infinitesimal. I am saying > this so you don't jump up out of your chair, yelling "HOORAY!" because I am > considering to use LLVM. Think of me as an academic student with too much > time on his hands, who is considering if he dares embark on the adventure of > getting to know LLVM. The way I see it, my life is going to be much easier > if I can delegate the responsibility for generating good code for a number > of targets to you guys and instead focus on what I am trying to do. Also, I > particularly like the aspect of global optimizations (link-time > optimizations) in LLVM - they're one of the selling features of my project. > > The project is a new programming language (http://www.braceless.org) for > which I have been contemplating writing my own backends, but the more I > think of it, the less I like the idea. I know you guys from earlier where I > posted a suggestion for an alternate implementation of exceptions (one that > uses only a single bit to indicate whether an exception has occured and then > uses the ordinary return value registers for the pointer to the exception > instance, in the rare event that an exception really happens) and it seems > to me that there's a natural match between what you do and what I'd like to > do. > > Now I at least have two problems: 1) I've written my "compiler" (language > parser, really) in C# and 2) I don't seem to be able to find any procedures > on building LLVM on Windows. The first problem is easy to solve; I'll > gladly recode my project in C++ just to get to use LLVM. The other problem > is a bit bigger, though: LLVM's Windows support. > > Do you plan to offer "true" Windows support - i.e. release > binaries/libraries for Windows and offer a build system that can be used on > Windows? Or is LLVM always going to be a mostly *nix-only project? > > IF LLVM already supports building on Windows, please don't flame me but > simply tell me in nice words that I am a moron and how to build LLVM for > Windows. I am mostly interested in native x86_64 support for Windows. > > If there's anything I can do to help, please don't hesitate to let me > know. I am on and off coding on portable build system written in C# for > .NET/Mono (portable to a wide variety of hosts), which I could perhaps some > day finish up and use to build the Windows release of LLVM. Perhaps I can > be of some value as a real-life tester of the Win64 backend? My initial > goal is to target Windows x64 first and then later on Windows x86, PPC, and > so on. > > P.S. I have a Windows 7 x64 box and a Debian 6.0 Linux 64-bit PPC box (an > ancient iMac G5 converted to a Linux box). I do know Linux and CAN work > under Linux, but I prefer to use Windows because of the popularity of this > platform and the fact that I have spent the last 20+ years working primarily > on the PC/Windows platform. > > P.P.S. I love writing documentation so I wouldn't mind putting together > some docs on how to get flying with LLVM on Windows. > > > Sincerely, > Mikael Lyngvig > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110220/b77bdcb5/attachment.html>
LLVM builds cross platform via CMake, I currently build/debug LLVM and Clang via VS2010 directly from the IDE. The libraries default to static link so they don't need separate distribution.x64 support is not quite their, but x86 is not bad. There are a number of people working on Windows related support for the project. There are instructions on windows builds at http://llvm.org/docs/GettingStartedVS.html. I checkout out trunk from the SVN server, then use CMake to generate a Visual Studio 2010 solution, and then build it from the IDE. On Sat, Feb 19, 2011 at 10:03 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:> Hi, > > This may be a daft question, but I have just begun taking a serious look at > LLVM for a project that I am working on. Knowing myself pretty well, the > probability that I ever complete the project is infinitesimal. I am saying > this so you don't jump up out of your chair, yelling "HOORAY!" because I am > considering to use LLVM. Think of me as an academic student with too much > time on his hands, who is considering if he dares embark on the adventure of > getting to know LLVM. The way I see it, my life is going to be much easier > if I can delegate the responsibility for generating good code for a number > of targets to you guys and instead focus on what I am trying to do. Also, I > particularly like the aspect of global optimizations (link-time > optimizations) in LLVM - they're one of the selling features of my project. > > The project is a new programming language (http://www.braceless.org) for > which I have been contemplating writing my own backends, but the more I > think of it, the less I like the idea. I know you guys from earlier where I > posted a suggestion for an alternate implementation of exceptions (one that > uses only a single bit to indicate whether an exception has occured and then > uses the ordinary return value registers for the pointer to the exception > instance, in the rare event that an exception really happens) and it seems > to me that there's a natural match between what you do and what I'd like to > do. > > Now I at least have two problems: 1) I've written my "compiler" (language > parser, really) in C# and 2) I don't seem to be able to find any procedures > on building LLVM on Windows. The first problem is easy to solve; I'll > gladly recode my project in C++ just to get to use LLVM. The other problem > is a bit bigger, though: LLVM's Windows support. > > Do you plan to offer "true" Windows support - i.e. release > binaries/libraries for Windows and offer a build system that can be used on > Windows? Or is LLVM always going to be a mostly *nix-only project? > > IF LLVM already supports building on Windows, please don't flame me but > simply tell me in nice words that I am a moron and how to build LLVM for > Windows. I am mostly interested in native x86_64 support for Windows. > > If there's anything I can do to help, please don't hesitate to let me > know. I am on and off coding on portable build system written in C# for > .NET/Mono (portable to a wide variety of hosts), which I could perhaps some > day finish up and use to build the Windows release of LLVM. Perhaps I can > be of some value as a real-life tester of the Win64 backend? My initial > goal is to target Windows x64 first and then later on Windows x86, PPC, and > so on. > > P.S. I have a Windows 7 x64 box and a Debian 6.0 Linux 64-bit PPC box (an > ancient iMac G5 converted to a Linux box). I do know Linux and CAN work > under Linux, but I prefer to use Windows because of the popularity of this > platform and the fact that I have spent the last 20+ years working primarily > on the PC/Windows platform. > > P.P.S. I love writing documentation so I wouldn't mind putting together > some docs on how to get flying with LLVM on Windows. > > > Sincerely, > Mikael Lyngvig > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110219/57f34cf8/attachment.html>
nullnull <null.function at gmail.com> writes:> I'm actively working on Windows with LLVM/clang (not directly contributing > yet). > > First of all, it does compile on Windows (only tested in Visual Studio > 2010). But, there are still many problems: > > (1) x86-64 won't compile as far as I know. CMake generates 64-bit soultion, > but one project is missing. But, 32-bit solution compiles safely.Building with VS for x86-64 used to work, and *should* work. If it doesn't, please create a bug report describing the problem.> (2) Although safe compiliation, there are many broken/unimplemented features > as of now. I can't detail everything. Some of them are very serious.If those problems are not on the bug database, please report them.> Currently, LLVM/clang on Windows is very experimental. I'm managed to make > it work.I'm successfully using the JIT on Windows (32 bits) since a long time ago. So the level of completeness of LLVM on Windows depends on your needs.> I believe the future of LLVM/clang on Windows is very promising. I'm trying > to report many bugs as much as I can, and also wish to contribute Windows > support!Looking forward to your contributions. But please keep in mind that a good report is a valuable contribution too.
Seemingly Similar Threads
- [LLVMdev] LLVM and Windows?
- [LLVMdev] Quad-Core ARMv7 Build Slave Seeks Noble Purpose
- [LLVMdev] GNU LLD build error? Seems that Clang likes LLD just fine.
- [LLVMdev] Quad-Core ARMv7 Build Slave Seeks Noble Purpose
- [LLVMdev] Quad-Core ARMv7 Build Slave Seeks Noble Purpose