Re: Visual C++ PGO linker memory usage

2013-05-23 Thread Jonas Sicking
Yes, this is indeed great stuff! Thank you so much for your work! / Jonas On Thu, May 16, 2013 at 2:03 PM, Boris Zbarsky wrote: > On 5/16/13 3:15 PM, Ted Mielczarek wrote: >> >> TL;DR: PGO on MSVC is now opt-in per-source-directory. > > > This is awesome. Thank you, Ehsan and Ted, for getting t

Re: Visual C++ PGO linker memory usage

2013-05-22 Thread papalowa
Woohoo! Great. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Visual C++ PGO linker memory usage

2013-05-16 Thread Boris Zbarsky
On 5/16/13 3:15 PM, Ted Mielczarek wrote: TL;DR: PGO on MSVC is now opt-in per-source-directory. This is awesome. Thank you, Ehsan and Ted, for getting this sorted out! -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://list

Re: Visual C++ PGO linker memory usage

2013-05-16 Thread Mike Hommey
On Thu, May 16, 2013 at 03:15:48PM -0400, Ted Mielczarek wrote: > Longer-term this should buy us more time for a real solution, as new > directories won't automatically contribute to the problem. We heard from > Microsoft that they are working on a 64-to-32-bit cross-toolchain, which > is the only

Visual C++ PGO linker memory usage

2013-05-16 Thread Ted Mielczarek
Hello friends, TL;DR: PGO on MSVC is now opt-in per-source-directory. Today I landed a patch[1] that significantly lowered the memory usage of the Visual C++ linker during PGO builds, which has been a consistent pain point for us. The ever-wonderful Ehsan got in touch with a VC++ program manager