search for: release_38

[ Original posting see [1] ] >From [1]: ... Added: llvm/tags/RELEASE_380/rc3/ (props changed) - copied from r261685, llvm/branches/release_38/ ... The LLVM Git repositories have no "rc3" tag in "release_38" branch (as an example llvm.git#release_38 see [2]). Who is responsible for that or maybe better... can you activate the responsible(s)...

On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > What you're probably missing is that 3.8.1 is made in release_38 > branch. So, everything is there and already mirrored. > > Source tarballs will be available upon the release. Which are just coming, now that final has been tested successfully. :) They'll be announced in the list and available here: http://llvm.org/releases/download.html#3.8.1 c...

On Sun, Jun 26, 2016 at 2:48 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> What you're probably missing is that 3.8.1 is made in release_38 >> branch. So, everything is there and already mirrored. >> >> Source tarballs will be available upon the release. > > Which are just coming, now that final has been tested successfully. :) > > They'll be announced in the list and available here: > > http://l...

...nch. On Wed, Feb 24, 2016 at 12:13 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Wed, Feb 24, 2016 at 7:49 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> [ Original posting see [1] ] >> >> From [1]: >> ... >> Added: >> llvm/tags/RELEASE_380/rc3/ (props changed) >> - copied from r261685, llvm/branches/release_38/ >> ... >> >> The LLVM Git repositories have no "rc3" tag in "release_38" branch (as >> an example llvm.git#release_38 see [2]). >> >> Who is responsible fo...

...-> 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 is it there? If there's no good reason, who has permission to remove it?

Hello , I have build llvm from release_38 branch ( only llvm and clang ) and install it. My DYLD_LIBRARY_PATH points to installation-directory/lib. I am compiling example files for Kaleidoscope with following command : clang++ -g toy.cpp -std=c++11 `llvm-config --cxxflags --ldflags --system-libs --libs core mcjit native` -O3 -o toy but...

...4 > = [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 is it there? If there's no good reason, who has permission to remove it? > ______________...

...ost basic test that should work. > The polly.sh script builds LLVM with static linkage and thus would create a libPolly.a, right? This cannot be loaded into 'opt' nor would 'opt' be linked with polly. I'd need a polly-enabled opt. I can try and build trunk (instead of the release_38 branch). Best, Frank > Best, > Tobias

>>> What you're probably missing is that 3.8.1 is made in release_38 >>> branch. So, everything is there and already mirrored. >>> >>> Source tarballs will be available upon the release. >> Which are just coming, now that final has been tested successfully. :) >> They'll be announced in the list and available here: >>...

On Mon, Jun 27, 2016 at 9:12 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >>>> What you're probably missing is that 3.8.1 is made in release_38 >>>> branch. So, everything is there and already mirrored. >>>> >>>> Source tarballs will be available upon the release. >>> Which are just coming, now that final has been tested successfully. :) >>> They'll be announced in the list and avai...

...e official release to happen, you will then find tarballs on llvm.org. They will also contain correct version strings, though I haven't yet tried building from the SVN branches directly. Maybe you need to use the SVN tags, $ clang --version currently gives me "clang version 3.8.0 (tags/RELEASE_380/final)") Jonas > -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Sedat > Dilek via llvm-dev > Sent: Monday, June 27, 2016 9:16 AM > To: Anton Korobeynikov > Cc: llvm-dev; Tom Stellard > Subject: Re: [llvm-dev] [LLVM/C...

Sedat, What you're probably missing is that 3.8.1 is made in release_38 branch. So, everything is there and already mirrored. Source tarballs will be available upon the release. On Sun, Jun 26, 2016 at 11:45 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > Hi Tom, Hi Anton, > > the first I had in mind was... > "Another (LLVM/CLang) realease...

Hi Tom, Hi Anton, the first I had in mind was... "Another (LLVM/CLang) realease - a new drama!" ( See Byron Katie "The work". ) I know SVN is your 1st development platform. Personally, I prefer Git and use the LLVM/Clang mirrors on GitHub. Unfortunately, I am missing a "release_381" branch at all on the GitHub repositories. I looked through the llvm-commits [1] and I only see two emails with the subject... "Creating release candidate final from release_381 branch" [test-suite] r273407 - Creating release candidate final from release_381 branch Tom Stellard...

I just checkout release_38 branches of llvm, clang and polly and built it on and x86 Ubuntu with cmake: CMAKE_BUILD_TYPE="Debug" CMAKE_INSTALL_PREFIX="$HOME/toolchain/install/llvm-3.8" LLVM_TARGETS_TO_BUILD="X86" cmake -G "Unix Makefiles" \ -DBUILD_SHARED_LIBS="ON" \ -DCMA...

...u will then find tarballs on >> llvm.org. They will also contain correct version strings, though I haven't yet >> tried building from the SVN branches directly. Maybe you need to use the SVN >> tags, $ clang --version currently gives me "clang version 3.8.0 >> (tags/RELEASE_380/final)") >> >> Jonas >> >>> -----Original Message----- >>> From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Sedat >>> Dilek via llvm-dev >>> Sent: Monday, June 27, 2016 9:16 AM >>> To: Anton Korobeynikov &gt...

> Can you answer my question on how to set the version-string correct > when generating tarballs out of the release_38 Git branch? > ( I generated source-tarballs out of my local Git repositories, see below. ) [ llvm.src/CMakeLists.txt ] ... if(NOT DEFINED LLVM_VERSION_MAJOR) set(LLVM_VERSION_MAJOR 3) endif() if(NOT DEFINED LLVM_VERSION_MINOR) set(LLVM_VERSION_MINOR 8) endif() if(NOT DEFINED LLVM_VERSION_PA...

According to the schedule (e.g. on the right on llvm.org), we should have tagged the release by now, but we haven't, so we're officially behind schedule. I'm still optimistic that we can wrap this up pretty soon, though. This is what's blocking us: - PR26509: Crash in InnerLoopVectorizer::vectorizeLoop() I'm waiting to hear what Cong comes up with, otherwise we can revert

...se to happen, you will then find tarballs on > llvm.org. They will also contain correct version strings, though I haven't yet > tried building from the SVN branches directly. Maybe you need to use the SVN > tags, $ clang --version currently gives me "clang version 3.8.0 > (tags/RELEASE_380/final)") > In the meantime I created source-tarballs out of my local Git repos and built a llvm-toolchain v3.8.1 successfully. I will test it with my local version of "llvmlinux-amd64" Linux-kernel. - Sedat - > Jonas > >> -----Original Message----- >> From:...

On 02/03/2016 10:41 AM, Tobias Grosser wrote: > On 02/03/2016 04:37 PM, Frank Winter wrote: >> Hi Tobias, >> >> I tried to invoke other passes and none of them are available, e.g.: >> >> ~/toolchain/install/llvm-3.8/bin/opt -load >> ~/toolchain/install/llvm-3.8/lib/libPolly.so -polly-cleanup >> >> opt: Unknown command line argument

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