search for: msvs2015

...t; >> For my project, timing is everything. We (and I could easily imagine, >> for many downstream projects) lead time is important. >> > > In Chromium land, we've so far been able to use the same compiler we use > to build Chrome to build clang. Currently that's MSVS2015 update 2, and it > took quite a while to update from 2013 to 2015 due bugs in 2015 and > whatnot. So I agree that it's useful to support older MSVS versions for > some time. For this reason, requiring update 3 would be inconvenient for > us, but 2015u2 would be no problem by now. It...

...> > For my project, timing is everything. We (and I could easily imagine, > > for many downstream projects) lead time is important. > > > > In Chromium land, we've so far been able to use the same compiler we use > to build Chrome to build clang. Currently that's MSVS2015 update 2, and it > took quite a while to update from 2013 to 2015 due bugs in 2015 and > whatnot. So I agree that it's useful to support older MSVS versions for > some time. For this reason, requiring update 3 would be inconvenient for > us, but 2015u2 would be no problem by now. It...

-----Original Message----- > From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org] On Behalf Of Aaron > Ballman via cfe-dev > Sent: Tuesday, August 02, 2016 12:06 PM > To: David Majnemer > Cc: llvm-dev; cfe-dev > Subject: Re: [cfe-dev] [llvm-dev] Revisiting our informal policy to > support two versions of MSVC > > On Tue, Aug 2, 2016 at 1:24 PM, David Majnemer via

...> > For my project, timing is everything. We (and I could easily imagine, > > for many downstream projects) lead time is important. > > > > In Chromium land, we've so far been able to use the same compiler we use > to build Chrome to build clang. Currently that's MSVS2015 update 2, and it > took quite a while to update from 2013 to 2015 due bugs in 2015 and > whatnot. So I agree that it's useful to support older MSVS versions for > some time. For this reason, requiring update 3 would be inconvenient for > us, but 2015u2 would be no problem by now. It...

...d easily imagine, > >> > >> for many downstream projects) lead time is important. > >> > >> > >> > >> In Chromium land, we've so far been able to use the same compiler we use > >> to build Chrome to build clang. Currently that's MSVS2015 update 2, and > it > >> took quite a while to update from 2013 to 2015 due bugs in 2015 and > whatnot. > >> So I agree that it's useful to support older MSVS versions for some > time. > >> For this reason, requiring update 3 would be inconvenient for us, but...

Erik de Castro Lopo wrote: > The think in and ideal world we would a: > > * Make it work correctly FLAC__BYTES_PER_WORD == 8 and compare the performance > with FLAC__BYTES_PER_WORD == 4. > * If there is an statistically measurable performance, keep it, otherwise > remove the FLAC__BYTES_PER_WORD == 8 code all together. I'll try to do it, but I don't have a deep

...ojects) lead time is important. > >> >> > >> >> > >> >> > >> >> In Chromium land, we've so far been able to use the same compiler we > >> >> use > >> >> to build Chrome to build clang. Currently that's MSVS2015 update 2, > and > >> >> it > >> >> took quite a while to update from 2013 to 2015 due bugs in 2015 and > >> >> whatnot. > >> >> So I agree that it's useful to support older MSVS versions for some > >> >> time. > &g...

...; >>> >> >> >>> >> >> >>> >> >> In Chromium land, we've so far been able to use the same compiler >>> we >>> >> >> use >>> >> >> to build Chrome to build clang. Currently that's MSVS2015 update >>> 2, and >>> >> >> it >>> >> >> took quite a while to update from 2013 to 2015 due bugs in 2015 and >>> >> >> whatnot. >>> >> >> So I agree that it's useful to support older MSVS versions for s...

...;>>> >> >> >>>>> >> >> In Chromium land, we've so far been able to use the same >>>>> compiler we >>>>> >> >> use >>>>> >> >> to build Chrome to build clang. Currently that's MSVS2015 update >>>>> 2, and >>>>> >> >> it >>>>> >> >> took quite a while to update from 2013 to 2015 due bugs in 2015 >>>>> and >>>>> >> >> whatnot. >>>>> >> >> So I ag...