Hi Kostya, > [did this go to lldb-dev on purpose?] > > Hi Pawel, > >>From these docs: > > > - ThreadSanitizer > (TSan)<http://llvm.org/releases/3.2/tools/clang/docs/ThreadSanitizer.html> > - > data race detector run-time library for C/C++ has been added. > - Improvemens to > AddressSanitizer<http://llvm.org/releases/3.2/tools/clang/docs/AddressSanitizer.html> > including: > increasing stack size limit to 256M, better portability > (iOS6,Windows,Android NDK), support for cmake based builds, enhanced error > reporting. > > > Both links point to nowhere.
Ah yes, for now it is kind of Back to the Future thingy. These links will work only after the 3.2 release has been created which did not happen yet but it will if we get it right. > AddressSanitizer's support for iOS and Windows is immature to include it > into release notes. Ok, I will remove it. > Did we do the "increasing stack size limit to 256M" bit? Commit log says so! '256M' bit? but who counts stack size in bits. Shall we say '256MB'? > > --kcc Thanks you for feedback! Pawel > > > > On Fri, Dec 14, 2012 at 4:35 AM, Chris Lattner <[email protected]> wrote: > >> The LLVM 3.2 release is wrapping up, and the 3.2 release notes are being >> finalized. There is a section describing improvements in LLVM 3.2 that >> could use some help, please take a look when you get a chance: >> >> http://llvm.org/viewvc/llvm-project/llvm/branches/release_32/docs/ReleaseNotes.html?revision=HEAD#lldb >> >> I think that improvements in linux support, in particular, may be worth >> highlighting along with the other general goodness that has happened since >> LLVM 3.1 branched. Feel free to commit improvements directly to the >> release_32 branch, or email Pawel text to include. >> >> -Chris >> _______________________________________________ >> lldb-dev mailing list >> [email protected] >> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev >> > _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
