similar to: [LLVM v3.8-rc2] New (tar)balls, please?

On Sat, Feb 6, 2016 at 12:34 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Sat, Feb 6, 2016 at 1:55 AM, Hans Wennborg <hans at chromium.org> wrote: >> On Fri, Feb 5, 2016 at 8:43 AM, Hans Wennborg <hans at chromium.org> wrote: >>> On Fri, Feb 5, 2016 at 12:48 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >>>> sorry, but I cannot

On Fri, Feb 5, 2016 at 8:43 AM, Hans Wennborg <hans at chromium.org> wrote: > On Fri, Feb 5, 2016 at 12:48 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> sorry, but I cannot see any tarballs shipped in [2]? >> Forgot to upload? >> >> Would like to give this pre-release a try on my Ubuntu/precise AMD64 system. > > They're not ready yet. It

On Thu, Mar 17, 2016 at 11:45 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Thu, Mar 17, 2016 at 10:05 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: >> [ brutal-snip ] >> ... >>> [ TODO#S: Before doing a 2nd build (and in a 3rd run using more >>>

Please have a look at the dedicated mailing list: http://lists.llvm.org/pipermail/llvm-branch-commits/ Please wait for the 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

The source tarball for clang-tools-extra-3.9.0.src.tar.xz is also missing as well from http://llvm.org/releases/3.8.1/. Jack On Tue, Jul 12, 2016 at 7:34 AM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > There is no compiler-rt v3.8.1 source tarball available on > <http://llvm.org/releases/3.8.1/>. > > - Sedat - > > On Mon, Jun 27, 2016 at

On Tue, Feb 17, 2015 at 1:55 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Tue, Feb 17, 2015 at 10:40 AM, Marc Dietrich <marvin24 at gmx.de> wrote: >> Patch 1 adds a check for the compilers visibility macro to configure.ac. >> Patch 2 avoids redefined symbol errors in clang of the tls entry points. >> Based on a suggestion from Rafael Ávila de Espíndola

> 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

On Mon, Jun 27, 2016 at 9:39 AM, Hahnfeld, Jonas <Hahnfeld at itc.rwth-aachen.de> wrote: > Please have a look at the dedicated mailing list: > http://lists.llvm.org/pipermail/llvm-branch-commits/ > OK, I clicked the offline version of that ML on the main-page of <llvm.org>, so I knew of it. Anyway, I think most people use Git these days. > Please wait for the official

Hmm, the clang+llvm-3.7.1-x86_64-sles11.3-linux-gnu.tar.xz tarball I uploaded doesn't seem to have made it on to this releases dir. I'm still a bit new to the process, is there a step that I skipped? On Wed, Jan 6, 2016 at 4:13 AM, Sedat Dilek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Mon, Jan 4, 2016 at 9:59 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote:

Thanks for the information Tobias. - Sedat - On Thu, Jan 24, 2019 at 3:31 PM Tobias Hieta <tobias at plexapp.com> wrote: > > Sedat, > > In Hans announcement yesterday he pointed out that he would upload source tarballs as soon as possible: > > "I'll get the source tarballs and docs published as soon as possible, and binaries as they become available" >

On Mon, Jun 27, 2016 at 12:14 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 27 June 2016 at 07:00, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> Building with CMake sets the version-string correct whereas using >> autotools as build-system does not. > > Hi Sedat, > > This was reported earlier and it's unfortunate, but we don't support

On Fri, Mar 4, 2016 at 11:28 AM, Tilmann Scheller <tilmann at osg.samsung.com> wrote: > Hi Sedat, > > On 03/03/2016 08:09 AM, Sedat Dilek via llvm-dev wrote: >> >> It might be that a CLANG generated with LTO/PGO speeds up the build. >> Can you confirm this? > > Yes, a Clang host compiler built with LTO or PGO is generally faster than an > -O3 build. >

On Wed, Apr 8, 2020 at 11:12 PM Sedat Dilek <sedat.dilek at gmail.com> wrote: > > On Wed, Apr 8, 2020 at 10:53 PM Nathan Chancellor > <natechancellor at gmail.com> wrote: > > > > When building with Clang + -Wtautological-compare and > > CONFIG_CPUMASK_OFFSTACK unset: > > > > Hi Nathan, > > thanks for the quick patch. > > I can confirm

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]

Signed-off-by: Sedat Dilek <sedat.dilek at gmail.com> --- CMakeLists.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index ed7aeb026f5d..60fe427e456e 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -66,7 +66,7 @@ set(LLVM_VERSION_PATCH 0) set(LLVM_VERSION_SUFFIX svn) if (NOT PACKAGE_VERSION) - set(PACKAGE_VERSION

Git tags and SVN tags are completely different beasts (git tag is simply a "second name" attached to revision, while on svn the tag could be arbitrary different). There is no way to automate the process - in general svn tag might not correspond (by contents) to any other revision in the repository. The only way to somehow emulate svn tags on git is to create a separate branch on each

Am Montag, 16. Februar 2015, 12:42:19 schrieb Sedat Dilek: > On Mon, Feb 16, 2015 at 10:39 AM, Marc Dietrich <marvin24 at gmx.de> wrote: > > Am Samstag, 14. Februar 2015, 18:20:12 schrieb Dimitry Andric: > >> On 11 Feb 2015, at 11:16, Sedat Dilek <sedat.dilek at gmail.com> wrote: > >> > On Wed, Feb 11, 2015 at 12:09 AM, Emil Velikov > >> >

LGTM. -Chris > On Feb 27, 2015, at 3:27 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > > Signed-off-by: Sedat Dilek <sedat.dilek at gmail.com> > --- > CMakeLists.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/CMakeLists.txt b/CMakeLists.txt > index ed7aeb026f5d..60fe427e456e 100644 > --- a/CMakeLists.txt > +++

On Tue, Feb 17, 2015 at 12:47 PM, Marc Dietrich <marvin24 at gmx.de> wrote: > Am Dienstag, 17. Februar 2015, 12:42:00 schrieb Sedat Dilek: >> On Tue, Feb 17, 2015 at 12:38 PM, Marc Dietrich <marvin24 at gmx.de> wrote: >> > Am Dienstag, 17. Februar 2015, 11:58:06 schrieb Sedat Dilek: >> >> On Tue, Feb 17, 2015 at 10:40 AM, Marc Dietrich <marvin24 at

Hi, when I switch to an unsupported GCC like v4.6.4 to build LLVM v3.8-rc3 with cmake I get the following: ... -- Looking for __atomic_fetch_add_4 in atomic -- Looking for __atomic_fetch_add_4 in atomic - not found CMake Error at cmake/modules/CheckAtomic.cmake:36 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first):