similar to: [LLVMdev] [MSVC] Adding LLVM build target support in VS2013 projects

On Tue, Oct 8, 2013 at 7:13 PM, Josh Samuel <JSamuel at iress.com.au> wrote: > I have attached a small patch from r192263 that I am using to add LLVM into > the toolchain for VS2013. > > Is someone able to review this and (if all good) submit to the source tree? I don't have VS2013 to verify this with, but the patch looks good and since it works for you, I've committed

Hi, It looks like I forgot to "svn add" the 2 targets files, and a typo appeared in the CMakelists.txt Fixes attached. "Works on my machine guarantee" ;-) Note - to actually compile the MSVC v120 header files will take a fair bit more work - there are a number of type traits not implemented by clang, that are breaking my MFC builds at the moment. (And a few compiler

On Wed, Oct 8, 2014 at 12:17 PM, Greg Bedwell <gregbedwell at gmail.com> wrote: > Hi, > > To follow up from Paul last week: > >> I'm expecting to have our internal builds switched over later this >> week. Our investigations have shown no problems. > > We've now updated our internal builds from 2012.4 (cl.exe 17.0.61030) to > 2013.3 (cl.exe

I've found that interception_win.cc line 835: "msvcr110.dll" //VS2012 "msvcr120.dll" //VS2013 interception is supported by commit 916b81 3 years ago , currently I'm build project with msvc100 , application will crash in un-intercepted free. adding msvcr100.dll to this list makes sanitizer working correctly , I wonder if compiler rt can including this msvc100.dll

If we have no other major users who require VS 2012 support, I think it's reasonable to officially switch now. We might want to wait for 3.6 to go out the door, just to reduce possible issues with porting fixes, but that may be overly cautious. ~Aaron On Wed, Jan 28, 2015 at 7:16 AM, Greg Bedwell <gregbedwell at gmail.com> wrote: > This thread seems to have stalled again without

lvqcl wrote: > Audacity still uses VS2008 and slowly tries to migrate to VS2012. > But as stated at <http://wiki.audacityteam.org/wiki/Developing_On_Windows>, > "Audacity is currently a 32-bit only application". So it doesn't need > 64-bit builds. > Currently its trunk contains 'audacity.sln' made with Visual C++ Express 2008 > and

Hi Martin, The key is available on the keys.gnupg.net key server. I'm also attaching it to this email for convenience. Would posting it on the release page really help? The user would still need to trust the page to trust the key. Thanks, Hans On Mon, Mar 2, 2015 at 5:58 AM, Richtarsky, Martin <martin.richtarsky at sap.com> wrote: > Hi Hans, > > I want to verify the

Daniel, Note the openmp library only has cmake build machinery preventing autoconf-based builds. Jack On Tue, Jun 23, 2015 at 10:18 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Hi, > > I'll do Mips as usual. Are we going to do an autoconf-based build for LLVM 3.7? If so, I might try Mips64 packages too. > >> -----Original

I'm using Windows 8.1, and every time I run check-clang, I eventually end up with a bunch of hung processes. Generally this is an instance of clang.exe, a bunch of instances of FileCheck.exe, and occasionally an llc.exe and an opt.exe. Inside, the processes are all hung inside of calls to WriteFile() attempting to write to stdout. I notice some of the tests fail with output indicating that

Final has been tagged, I think we're about to release it. On Fri, Feb 27, 2015 at 7:43 AM, Hayden Livingston <halivingston at gmail.com> wrote: > Are we waiting for an RC5? It seems like the release mirror on github has > no recent activity. > > On Wed, Feb 25, 2015 at 3:23 AM, Daniel Sanders <Daniel.Sanders at imgtec.com > > wrote: > >> Quick update

Hello, Today we hit another VS 2013 breakage < http://lab.llvm.org:8011/builders/sanitizer-windows/builds/26666/steps/run%20tests/logs/stdio> which results us having to alter LLVM. While we have no documented policy of supporting two version of MSVC, we do have an informal agreement that we should support the last two versions. I suggest that we alter our informal policy to the following:

On Fri, Aug 3, 2018 at 3:38 PM, <paul.robinson at sony.com> wrote: > Hi Hans, > > I was just trying to push a release note about DWARF v5 support. I did: > git checkout release_70 # in the monorepo > git commit <update to llvm/docs/ReleaseNotes.rst> > git llvm push > but that fails. How do you want to do release notes? I'm not familiar with "git

Hi Daniel, Thanks for trying out the branch :-) On Fri, Jan 15, 2016 at 5:30 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Hi Hans, > > I tried the release branch last night and I'm having problems building it. The problem is that test-suite is now building as part of the Phase[123] builds (because this project contains CMakeLists.txt's now) but cmake 3.0.2

On Mon, Feb 9, 2015 at 8:36 AM, Greg Bedwell <gregbedwell at gmail.com> wrote: > We've just encountered an issue with ninja and VS2013 when using versions of > CMake prior to 2.8.12.1. This isn't a combination that we typically use so > we've not run into it previously in our own builds. It isn't specifically > tied to upgrading the minimum version as it's a

Quick update before I move on to the final tag. > clang+llvm-3.6.0-rc4-mipsel-linux-gnu.tar.xz > Still running due to a silly setup mistake on the first run (a broken > symlink to the test-suite source). Second attempt is a fair way through and > looks good so far though Default options were all good. Mips32 was about halfway but was good so far. >

Hans, Daniel, How are things going? It's been 5 days and no word. I'm running the tests now, just in case, but would be good to know that no one would be committing to the release candidate 1 tree in the mean time. cheers, --renato On 15 January 2016 at 15:56, Daniel Sanders via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> -----Original Message----- >> From:

Hello testers, RC4 has just been tagged (at r229782 on the branch). RC3 was disqualified due to an infloop that Duncan reported, and fixed in r229421. That, fixes for a few scary X86 bugs, a GCC5 bootstrap problem (PR22625), and parts of PR22589 is included in RC4. Baring any showstoppers, this release candidate will be promoted to release. Please let me know how it looks and upload binaries

Dear everyone, It's not quite time to start the 3.8 release process, but it's time to start planning. Please let me know if you want to help with testing and building release binaries for your favourite platform. (If you were a tester on the previous release, you're cc'd on this email.) I propose the following schedule for the 3.8 release: - 13 January: Create 3.8 branch.

We got everything, haven't we? On 26 February 2015 at 20:44, Nikola Smiljanic <popizdeh at gmail.com> wrote: > Final has been tagged, I think we're about to release it. > > On Fri, Feb 27, 2015 at 7:43 AM, Hayden Livingston <halivingston at gmail.com> > wrote: >> >> Are we waiting for an RC5? It seems like the release mirror on github has >> no

Currently, LLVM_HAS_INITIALIZER_LISTS is set based on __has_feature(cxx_generalized_initializers) && !defined(_MSC_VER) Based on the docs, we should be able to drop the _MSC_VER check now that we've moved to VS2013. Can somebody confirm that? The other problem is that GCC doesn't recognize __has_feature, so this is essentially only enabled for clang. If we're keeping this