similar to: [LLVMdev] [3.0 Release] Call for External Open Source Projects Using LLVM 3.0

Another one: Name: SDC - The Stupid D Compiler (https://github.com/bhelyer/SDC) Description: A project seeking to write a self-hosting compiler for the D programming language, without using the frontend of the reference compiler (DMD). Regards, Alex On Tue, Oct 25, 2011 at 3:06 AM, Bill Wendling <wendling at apple.com> wrote: > Good day! > > To get ready for the release, we need

On Tue, Oct 25, 2011 at 5:06 AM, Bill Wendling <wendling at apple.com> wrote: > Good day! > > To get ready for the release, we need to make sure that the list of external open source projects using LLVM 3.0 (file:///Volumes/Sandbox/llvm/llvm.src/docs/ReleaseNotes.html#externalproj) is up to date. Please send me an email with the project's name and a short description of it.

Hi All, With 2.9 starting to make its way out into the world, it is time to start poking at the release notes. I plan to make a pass through llvm-commits to cull some of the major changes into bullets, but am already behind and insanely busy with other stuff over the next week. If you have commit access, I'd really appreciate it if you could take a pass through llvm/docs/ReleaseNotes.html

Hi all! Please remember to update the release notes! We're getting close to the release date, and we need the notes to be up-to-date. Also, if you have a project which uses LLVM, please send me a blurb about it and I can add it to our "external projects" list (or, if you have commit access, you can add it). Thanks! -bw

On Wed, Oct 26, 2011 at 12:33 PM, Alexander Potapenko <ramosian.glider at gmail.com> wrote: > On Tue, Oct 25, 2011 at 5:06 AM, Bill Wendling <wendling at apple.com> wrote: >> Good day! >> >> To get ready for the release, we need to make sure that the list of external open source projects using LLVM 3.0

The LLVM 3.2 release is winding down, and that means release notes! There are two pieces to this. First, if you're an external LLVM user, we'd like to list you as such in the release notes. This is a great way to get some free advertisement. The section is here: http://llvm.org/viewvc/llvm-project/llvm/branches/release_32/docs/ReleaseNotes.html?revision=HEAD#externalproj Please email

On 11.05.2012, at 22:55, Bill Wendling wrote: > Hi all! > > Please remember to update the release notes! We're getting close to the release date, and we need the notes to be up-to-date. I added some bigger picture notes to http://llvm.org/docs/ReleaseNotes.html this morning, but we're still missing a lot of text, specifically: - clang: clang has it's own release notes

If your project works with LLVM 2.7 and you want it included in the release notes, please email me a blurb to include ASAP. -Chris

Hi All, I've finished the first draft of the 2.8 release notes: http://llvm.org/docs/ReleaseNotes.html Please feel free to commit improvements and enhancements. There are "a lot" of changes that went into 2.8, but I think I've scraped most of them out of the commits. However, it is also highly likely that I missed something, so if I missed your favorite feature, please speak

On 2010-10-04 06:43, Chris Lattner wrote: > Hi All, > > I've finished the first draft of the 2.8 release notes: > http://llvm.org/docs/ReleaseNotes.html > > Please feel free to commit improvements and enhancements. There are "a lot" of changes that went into 2.8, but I think I've scraped most of them out of the commits. However, it is also highly likely that I

Hey, Do you want projects which specifically use LLVM 3.1 or just LLVM in general? Regards, Alex On Fri, May 11, 2012 at 10:55 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all! > > Please remember to update the release notes! We're getting close to the release date, and we need the notes to be up-to-date. > > Also, if you have a project which uses LLVM, please

Hello, While instrumenting LLVM IR in ThreadSanitizer (race detector), I need to distinguish between a store to vtable pointer (vptr) and any other regular store. This special treatment should be limited to class DTORs, so I should also know when a function is a DTOR. Rationale: need to distinguish benign and harmful races on vptr (

The first draft of the LLVM 3.0 release notes now done, in llvm/docs/ReleaseNotes.html (the web page isn't autoupdating at the moment). Please take a look and make corrections or enhancements as you see fit. There are still a few things that I need from specific people (marked with XXX's): - BillW is writing a blog about exception handling. - The llvm.expect intrinsic isn't documented

Ok, the LLVM 2.7 release notes are in near final shape. Please take a look and suggest improvements (or, better yet, just commit improvements if you have commit access): http://llvm.org/docs/ReleaseNotes.html Things still needed are marked with FIXMEs. These include: 1. Clang needs a blurb describing what's new in 2.7. Have the clang folks been doing anything for the last 6 months? 2. I

This is a new build failure as of today. Does this look familiar to anyone? -bw llvm[2]: Compiling CommonProfiling.ll to CommonProfiling.bc for Debug build (bytecode) Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter

On 05/24/2012 03:37 AM, Michael Spencer wrote: > LLVM already supports Windows quite well. The issue is clang and the > MS C++ ABI. If you are writing your own language that does not need to > interact with the C++ ABI then everything will be fine. I can confirm this. Even if you do need to interface to C/C++, clang works fine for that as long as you stick to the mingw libraries instead

Dear everyone, The in-progress release notes for 3.7 [1,2] make it look like we didn't do very much over the past six months. Obviously that's not the case at all, so let's get them in shape! If you've been thinking "I should probably add this to the release notes at some point", now is the time :-) I have a list below of changes that might be worth mentioning. I

A debug or release build? -bw On Sep 24, 2007, at 2:36 PM, Dale Johannesen wrote: > > On Sep 24, 2007, at 2:29 PM, Bill Wendling wrote: > >> Hi all, >> >> Did someone forget to check-in a patch? I'm getting this error during >> compilation on PPC: > > A recent checkout compiled fine for me (on x86). > >>

Hi all, Did someone forget to check-in a patch? I'm getting this error during compilation on PPC: /Volumes/SandBox/Clean/llvm-9999-01.roots/llvm-9999-01~obj/src/llvm/lib/Analysis/IPA/Andersens.cpp: In function 'void dumpToDOUT(llvm::SparseBitVector<128u>*)': /Volumes/SandBox/Clean/llvm-9999-01.roots/llvm-9999-01~obj/src/llvm/lib/Analysis/IPA/Andersens.cpp:1189: error: no

Hi, I keep getting this error during compilation: llvm[2]: ======= Finished Linking Debug Executable llvm-dis llvm[2]: Compiling opt.cpp for Debug build llvm[2]: Linking Debug executable opt /usr/bin/ld: Undefined symbols: llvm::PATypeHolder::get() const collect2: ld returned 1 exit status make[2]: *** [/Users/wendling/llvm/llvm/Debug/bin/opt] Error 1 make[1]: *** [opt/.makeall] Error 2 make: