similar to: [LLVMdev] Fail to build LLVM release_36 in MSVC 2013

Hi Hans, I have attached a unit test which demonstrates a hang/infinite loop with the opt built with release_36 sources. The fixes are already pushed to "master" branch. The revisions r226588 and r226616 should be pushed to release_36 to fix the unit test. --Sumanth G -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, Could someone please tell me why LLVM and clang downloaded from here: svn co http://llvm.org/svn/llvm-project/llvm/trunk llvmsvn co http://llvm.org/svn/llvm-project/cfe/trunk clang and generated using cmake: cmake -G "Visual Studio 15 2017" ../llvm does not compile in Visual Studio? I am using Batch Build in Visual Studio and I have selected only ALL_BUILD project to build as

The 3.6 release is drawing nearer, but the release notes could still use a lot of improvement: LLVM: https://github.com/llvm-mirror/llvm/blob/release_36/docs/ReleaseNotes.rst Clang: https://github.com/llvm-mirror/clang/blob/release_36/docs/ReleaseNotes.rst The good news is that they can be updated all the way up until release. If you have a patch for the release notes, commit it directly to the

> In conclusion: > Why are people using Git disadvantaged? Short answer: because of git-svn and differences between what is a tag in git and svn. Long answer: git-svn never created proper git tags. Instead, it converted svn tags to branches (because technically branches and tags are same in svn). These branches were orphan and not usable for bunch of things (I believe Takumi can provide a

On Mon, Feb 9, 2015 at 9:47 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hans, > >>> I see a Git branch "release_36", but what has v3.6.0rc2 for a >>> commit-id, can you tags that? >>> No, there are no tags at all @ github. >> >> Anton, is it possible to translate the svn tags to git tags? > In the past we had problems

I.e., I see this when I run `git fetch`: ``` $ git fetch -v llvm.org From http://llvm.org/git/llvm = [up to date] master -> llvm.org/master = [up to date] release_1 -> llvm.org/release_1 = [up to date] release_16 -> llvm.org/release_16 = [up to date] release_20 -> llvm.org/release_20 = [up to date] release_21 -> llvm.org/release_21 = [up to date]

Hi, is it possible to have appropriate tags for the Git repositories @ github? I see a Git branch "release_36", but what has v3.6.0rc2 for a commit-id, can you tags that? No, there are no tags at all @ github. Can you add in your announces a svn-trunk revision next time (for rc3)? Somehow it should be clear what is "rc2". Thanks. Regards, - Sedat -

> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: > > That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. > It can be deleted now, if anyone wants to. ``` $ git push llvm.org :release_35 at 215010 fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested

Hi, I don't see the release_36 branch in http://llvm.org/git/llvm.git or in the github mirror https://github.com/llvm-mirror/llvm/branches Is this a mistake, something still to be done, or is it a change from previous releases? -- Quentin -------------- next part -------------- An HTML attachment was scrubbed... URL:

Done: http://llvm.org/viewvc/llvm-project/cfe/branches/release_36/docs/ReleaseNotes.rst?view=markup#l113 We've been technically able to self-host for a some time, but now it's simple as 'CC=clang-cl CXX=clang-cl cmake'. =D On Wed, Feb 25, 2015 at 3:00 PM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > Nice. This should probably go to on the release notes :-)

On 19 Jul 2015, at 00:17, Dimitry Andric <dimitry at andric.com> wrote: > > On 17 Jul 2015, at 01:09, Hans Wennborg <hans at chromium.org> wrote: >> >> On Thu, Jul 16, 2015 at 3:47 PM, Dimitry Andric <dimitry at andric.com> wrote: >>> On 17 Jul 2015, at 00:31, Hans Wennborg <hans at chromium.org> wrote: >>>> >>>> Dear

Hi Anton, It seems that some release branches (e.g. release_30, release_35, and release_36) are missing from the Git mirror for libc++abi. May you help to fix the problem? Thanks. Sincerely, Logan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150201/68faf5d4/attachment.html>

Hi, Please point me to where I can find informaion on the following message that I get when I compile theora beta 2 in VS2005: "fatal error C1189: #error : You are compiling theora without inline assembly. This is probably not what you want. Instead, please either (1) download the assembly .lib binaries or (2) compile them yourself using MinGW, and make Visual Studio link against them.

Hey guys, I''m running the mongrel server that comes with rails-1.2rc1 for development on a winxp box, anticipating taking it into production on a win2k3 box in the next few weeks. I''ve had a couple of crashes occur during development that give me pause, however. I made a ticket for the last one here: http://dev.rubyonrails.org/ticket/6841 I know, or at least believe, that

On Sun, Jul 19, 2015 at 8:32 AM, Dimitry Andric <dimitry at andric.com> wrote: > On 19 Jul 2015, at 01:44, Dimitry Andric <dimitry at andric.com> wrote: > ... >> Hm, strangely enough, this version of the script does not go further than the Phase 2 installation, and does not run any tests? This used to work fine for the release_36 branch. >> >> I think it is

Hi Martin, On Fri, 3 Aug 2018 at 14:10, Martin J. O'Riordan <MartinO at theheart.ie> wrote: > $ git branch --list > * master > martino By default "git branch" only lists local branches. "git branch -a" will list all of them, including (for me) "remotes/origin/release_70". If you just type "git checkout release_70" git will

On Thu, Jul 16, 2015 at 3:47 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 17 Jul 2015, at 00:31, Hans Wennborg <hans at chromium.org> wrote: >> >> Dear testers, >> >> 3.7.0-rc1 was just tagged; please start your testing engines :-) >> >> Upload binaries to the sftp and report your results to this thread. >> >> I'm sorry

On Wed, Feb 18, 2015 at 3:01 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 18 February 2015 at 19:52, Jack Howarth > <howarth.mailing.lists at gmail.com> wrote: >> Assuming that the clang-omp >> developers can find time to rebase their upstream tree on the new 3.6 >> release, I intend to do the same for the fink llvm36 packaging. So >> yes, a

On 19 Jul 2015, at 17:32, Dimitry Andric <dimitry at andric.com> wrote: > > On 19 Jul 2015, at 01:44, Dimitry Andric <dimitry at andric.com> wrote: > ... >> Hm, strangely enough, this version of the script does not go further than the Phase 2 installation, and does not run any tests? This used to work fine for the release_36 branch. >> >> I think it is

Over the weekend I had a random urge to make clang-cl be able to self host. As of r230539, this should now be possible. Steps to try this out: 1) Run vcvarsall.bat, same as you would for an MSVC hosted build. 2) set CC=CXX=clang-cl (make sure it's in your path 3) Run CMake as you normally would, no special flags needed. 4) There is no 4, that's it! Currently LLD will not build, so if