search for: vs2015

--- win32/VS2015/opus.vcxproj | 2 ++ win32/VS2015/opus.vcxproj.filters | 6 ++++++ 2 files changed, 8 insertions(+) diff --git a/win32/VS2015/opus.vcxproj b/win32/VS2015/opus.vcxproj index d9aaa03..f55ea37 100644 --- a/win32/VS2015/opus.vcxproj +++ b/win32/VS2015/opus.vcxproj @@ -852,6 +852,7 @@ <...

Avoids trying to create and replace version.h more than once which led to file-locking errors with multicore builds. --- Makefile.am | 1 + win32/VS2015/celt.vcxproj | 48 +++++++++++++++++--------- win32/VS2015/generate_version.vcxproj | 65 +++++++++++++++++++++++++++++++++++ win32/VS2015/opus.sln | 32 ++++++++++++++++- win32/VS2015/opus.vcxproj | 48 +++++++++++++++++--------- win32/VS2015/silk_common.vcx...

...the files don't exist. --- appveyor.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appveyor.yml b/appveyor.yml index c85b0b1..ad9c6c0 100644 --- a/appveyor.yml +++ b/appveyor.yml @@ -17,7 +17,7 @@ build: verbosity: minimal after_build: -- cmd: 7z a opus.zip win32\VS2015\%PLATFORM%\%CONFIGURATION%\opus.lib include\*.h +- cmd: 7z a opus.zip win32\VS2015\%PLATFORM%\%CONFIGURATION%\opus.lib include\*.h -i!win32\VS2015\%PLATFORM%\%CONFIGURATION%\opus.dll -i!win32\VS2015\%PLATFORM%\%CONFIGURATION%\opus.exp test_script: - cmd: >- -- 2.9.1

AFAICT we traditionally only support building llvm/clang with the 2 most recent releases of Visual Studio. With the release of VS2019, what do people think of retiring VS2015 support before the next major llvm/clang release? As well as simplifying C++14 migration (admittedly only a little), this should also let us remove a number of hacks (e.g. the alignas/AlignedCharArray hack in AlignOf.h), as well as re-enabling a number of warnings in HandleLLVMOptions.cmake....

Orestes Zoupanos wrote: > VS2015, considering it's quite recent and the Community Edition has a > free-to-use-for-open-source license going on. > >>> Yup, into win32\VS2010 and VS2015. >> >> VS2015 or VS2005? Currently FLAC has 2 Visual Studio solutions: one >> for VS2005 >> (and 2008) a...

Not 100% if this is an LLVM question or a CLang question, though I expect LLVM. On Linux, if I pass '-fsave-optimization-record' to 'clang', then it produces a '*.opt.yaml' file. However, the same thing run on Windows using 'clang' built with VS2015 silently ignores this option. Is this a bug or is it intentional? And if it is intentional, how can I configure and build on Windows to enable this feature? Thanks, MartinO -------------------------------------------------------------- Intel Research and Development Ireland Limited...

Hi all, Firstly sorry I'm a bit late responding on this one. Internally to ARM we build LLVM for Windows. Our current build cluster has only VS2013 installed and as a result of this thread we've been working on getting VS2015 installed. This involves a certain amount of IT-wrangling as the cluster we use is company-wide. There have been some hiccups regarding licensing of MSVC professional (we can't use the community edition for the same reasons mentioned by Paul previously) but we hoped to be ready in time for the...

There are certainly enough people making commits that work with VS2015 but not VS2013 that the "would it be useful" question is pretty well answered. I've already brought up the idea on my team, as it's obviously coming and we need time to coordinate with internal consumers of the toolchain. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists....

Erik de Castro Lopo wrote: >> I'm looking to maybe move all the .sln and related Visual Studio project >> files (not the source .c and .h files!) into new directories under >> "win32\*" within the flac reppo. >> Any objections/tips or reasons to leave them as is? > > Lvqcl and other Windows devs? > > I'm ok with this if you are. I don't

VS2015, considering it's quite recent and the Community Edition has a free-to-use-for-open-source license going on. On 16/05/2016 16:53, lvqcl wrote: > Orestes Zoupanos wrotw: > >> Yup, into win32\VS2010 and VS2015. > > VS2015 or VS2005? Currently FLAC has 2 Visual Studio solutions...

...ts.llvm.org> wrote: > >> Hi all, >> >> Firstly sorry I'm a bit late responding on this one. Internally to ARM we >> build LLVM for Windows. Our current build cluster has only VS2013 installed >> and as a result of this thread we've been working on getting VS2015 >> installed. This involves a certain amount of IT-wrangling as the cluster we >> use is company-wide. There have been some hiccups regarding licensing of >> MSVC professional (we can't use the community edition for the same reasons >> mentioned by Paul previously) but w...

...ion last time was his. On Fri, Jul 29, 2016 at 2:00 PM Sean Silva <chisophugis at gmail.com> wrote: > On Fri, Jul 29, 2016 at 1:23 PM, Robinson, Paul via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> There are certainly enough people making commits that work with VS2015 >> but not VS2013 that the "would it be useful" question is pretty well >> answered. I've already brought up the idea on my team, as it's obviously >> coming and we need time to coordinate with internal consumers of the >> toolchain. >> > > Als...

...ct: Re: [llvm-dev] Upgrading to MSVC 2015 > > There are not that many people making commits to working around MSVC > 2013 as I think are claimed CGOpenMPRuntime.cpp had 4 patches this week trying to make VS2013 happy. I can tell they were because of VS2013 because the public PS4 bot has VS2015 and it didn't seem to have the same problems. Maybe it was just bad luck that we put up an internal VS2013 bot when it happened, but it has been an incredible time-sink for me this week. Note I do not want to advance the timetable, I just want to make sure that the actual problems aren't d...

https://www.visualstudio.com/en-us/news/vs2015-vs.aspx Is it time? 2016-03-31 12:03 GMT-07:00 Aaron Ballman via llvm-dev < llvm-dev at lists.llvm.org>: > On Thu, Mar 31, 2016 at 2:57 PM, Zachary Turner <zturner at google.com> > wrote: > > > > > > On Tue, Mar 29, 2016 at 10:42 AM Aaron Ballman <aaron at...

...Fri, Jul 29, 2016 at 2:00 PM Sean Silva <chisophugis at gmail.com> wrote: >> >> On Fri, Jul 29, 2016 at 1:23 PM, Robinson, Paul via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> >>> There are certainly enough people making commits that work with VS2015 >>> but not VS2013 that the "would it be useful" question is pretty well >>> answered. I've already brought up the idea on my team, as it's obviously >>> coming and we need time to coordinate with internal consumers of the >>> toolchain. >&g...

...gt;> Hi all, >>> >>> Firstly sorry I'm a bit late responding on this one. Internally to ARM >>> we build LLVM for Windows. Our current build cluster has only VS2013 >>> installed and as a result of this thread we've been working on getting >>> VS2015 installed. This involves a certain amount of IT-wrangling as the >>> cluster we use is company-wide. There have been some hiccups regarding >>> licensing of MSVC professional (we can't use the community edition for the >>> same reasons mentioned by Paul previously) bu...

On Fri, Jul 29, 2016 at 1:23 PM, Robinson, Paul via llvm-dev < llvm-dev at lists.llvm.org> wrote: > There are certainly enough people making commits that work with VS2015 but > not VS2013 that the "would it be useful" question is pretty well answered. > I've already brought up the idea on my team, as it's obviously coming and > we need time to coordinate with internal consumers of the toolchain. > Also, we have an increasing number of...

I downloaded 3.8.0rc3 and I also have it in 3.8.0rc3. I did set a data access breakpoint on the first function ptr that causes the invalid heap. This would allow me to break whenever someone is touching that address. It did not show double deletes during debugging. Further more I managed to narrow it down to 2 function calls: // stupid code, but its just for triggering heap error auto func =

...to MSVC 2015 >> >> There are not that many people making commits to working around MSVC >> 2013 as I think are claimed > > CGOpenMPRuntime.cpp had 4 patches this week trying to make VS2013 happy. > I can tell they were because of VS2013 because the public PS4 bot has > VS2015 and it didn't seem to have the same problems. Hmmm, I don't see any mention in the code itself about changes to appease MSVC 2013, so that's why it didn't come up in my searches. We usually ask people working around buggy compilers to leave a FIXME in there so we can remove compile...

...1:07 PM, Robinson, Paul <paul.robinson at sony.com> wrote: > Hi Reid, first off thanks *very* much for all your help fixing > 2013-related problems. We really appreciate it. > > > > Let me propose a target date of September 15 for advancing the minimum MS > compiler to VS2015 Update 3. Certainly my team should be ready by then. If > anybody else needs a later date, in particular people who own Windows bots > still using VS2013, please speak up. > > --paulr > > > > *From:* Reid Kleckner [mailto:rnk at google.com] > *Sent:* Wednesday, August 31...