search for: release_36

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 branch, or send it to me and I'll commit it for y...

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: <http://lists.llvm.org/pipermail/llvm-dev/...

> 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 with git-svn tags, so we decided to go > with branche...

Hi, All, I follow the menu http://llvm.org/docs/GettingStartedVS.html , but still failed to build LLVM debug version. Here's error message: 7>C:\study\llvm\projects\compiler-rt\lib\asan\asan_win.cc(69): fatal error C1189: #error : Please build the runtime with a non-debug CRT: /MD or /MT Any idear? -- Best Regards, Amy -------------- next part -------------- An HTML attachment was

...-> llvm.org/release_32 = [up to date] release_33 -> llvm.org/release_33 = [up to date] release_34 -> llvm.org/release_34 = [up to date] release_35 -> llvm.org/release_35 = [up to date] release_35 at 215010 -> llvm.org/release_35 at 215010 = [up to date] release_36 -> llvm.org/release_36 = [up to date] release_37 -> llvm.org/release_37 = [up to date] release_38 -> llvm.org/release_38 = [up to date] stable -> llvm.org/stable = [up to date] testing -> llvm.org/testing ``` The release_35 at 215010 looks bogus. Why i...

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 -

...2 > = [up to date] release_33 -> llvm.org/release_33 > = [up to date] release_34 -> llvm.org/release_34 > = [up to date] release_35 -> llvm.org/release_35 > = [up to date] release_35 at 215010 -> llvm.org/release_35 at 215010 > = [up to date] release_36 -> llvm.org/release_36 > = [up to date] release_37 -> llvm.org/release_37 > = [up to date] release_38 -> llvm.org/release_38 > = [up to date] stable -> llvm.org/stable > = [up to date] testing -> llvm.org/testing > ``` > The release_35...

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: &l...

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 prob...

...eplaced the multiple calls to uname -s with a variable assignment. > > It's currently building for FreeBSD 10.x i386 and amd64. 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 because of the "set -o pipefail" which was introduced, but I don't yet understand why this causes the Phase 2 installation to appear to fail, as there is no visible error. I will investigate, or work around it by removing the pipefail option again. -Dimitry -...

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>

...c <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 because of the "set -o pipefail" which was introduced, but I don't yet understand why this causes the Phase 2 installation to appear to fail, as there is no visible error. I will investigate, or work around it by removing the pipefail option ag...

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

...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 because of the "set -o pipefail" which was introduced, but I don't yet understand why this causes the Phase 2 installation to appear to fail, as there is no visible error. I will investigate, or work around it by removing the pipefail option a...

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