similar to: LLVM/Clang version 7.0.0rc2 fails with gcc (Debian 8.2.0-4)

On Tue, Aug 28, 2018 at 10:26 AM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Mon, Aug 27, 2018 at 6:09 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> Hi, >> >> I have not sent yet any bug-reports to llvm-dev but I am seeing this >> build-failure: >> >> ... >> [574/3685] Building CXX object >>

On 28.08.2018 13:55, Sedat Dilek wrote: > On Tue, Aug 28, 2018 at 10:59 AM, Hans Wennborg <hans at chromium.org> wrote: >> On Tue, Aug 28, 2018 at 10:26 AM, Sedat Dilek via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> On Mon, Aug 27, 2018 at 6:09 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >>>> Hi, >>>> >>>>

On Wed, Aug 29, 2018 at 9:29 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Wed, Aug 29, 2018 at 7:51 AM, Matthias Klose <doko at debian.org> wrote: >> On 28.08.2018 13:55, Sedat Dilek wrote: >>> On Tue, Aug 28, 2018 at 10:59 AM, Hans Wennborg <hans at chromium.org> wrote: >>>> On Tue, Aug 28, 2018 at 10:26 AM, Sedat Dilek via llvm-dev

On Wed, Aug 29, 2018 at 10:14 AM, Hans Wennborg <hans at chromium.org> wrote: > On Wed, Aug 29, 2018 at 9:45 AM, Sedat Dilek via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi, >> >> for filing a GCC v8.2.0 bug in Debian/buster AMD64 the Debian/GCC >> mainatiners want two things... >> >> [ FULL CMAKE LINE ] >> >> How do I

Hi, for filing a GCC v8.2.0 bug in Debian/buster AMD64 the Debian/GCC mainatiners want two things... [ FULL CMAKE LINE ] How do I configure this in the LLVM/Clang build? Can I set an option of cmake? [ PREPROCESSED SOURCE FILES ] How and where do I get the preprocessed source? Do I need to set options for this in my build-script? My build-script is attached. Thanks in advance. Regards, -

On Mon, May 7, 2018 at 4:03 PM, Amara Emerson <aemerson at apple.com> wrote: > On 7 May 2018, at 11:01, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> > wrote: > > On Mon, May 7, 2018 at 5:52 AM, Brian Cain <brian.cain at gmail.com> wrote: > > The simplest way to run a clang test case that I know of is to clone both > llvm and clang repos, run all the

On Mon, May 7, 2018 at 10:13 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > ... > > sdi at iniza:~/src/llvm-toolchain/build$ ./bin/llvm-lit -v > ./tools/clang/test/Sema/asm.c > llvm-lit: /home/sdi/src/llvm-toolchain/llvm/utils/lit/lit/llvm/ > config.py:334: > note: using clang: /home/sdi/src/llvm-toolchain/build/bin/clang > -- Testing: 1 tests, 1 threads --

Hi, while experimenting with llvmlinux on Debian/testing AMD64 I wanted to run some x86-64 ASM tests. I fell over [1] and wanted to run it. So, I cloned clang from Git... $ git clone https://github.com/llvm-mirror/clang.git I looked through some docs where I have seen I need "llvm-lit" or "lit.py". The Debian package llvm-7-tools from <apt.llvm.org> does ship

Yeah, I see. You have an unusual development process seen from my POV. IMHO you can provide the tarballs before the "binaries" are uploaded which means "prebuilt binaries". That could increase the quality of developing when different arch/os maintainers give their OK. But for 7.0.0rc1 I see only prebuilt binaries for... * macOS * FreeBSD10 AMD64 * Windows (32-bit) * Windows

On Mon, Aug 27, 2018 at 10:30 AM, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: > On 2018-08-27 09:44, Sedat Dilek wrote: >> >> Yeah, I see. >> You have an unusual development process seen from my POV. > > > GNOME does the same, to pick one example: > https://wiki.gnome.org/ThreePointTwentynine > Tarballs are due on Monday, official release and announcement

Hi, I have seen you tagged 7.0.0rc2 in SVN, but [1] has no tarballs for downloading? Can you please provide them? Thanks in advance. Regards, - Sedat - [1] http://prereleases.llvm.org/7.0.0/#rc2 [2] https://lists.llvm.org/pipermail/llvm-branch-commits/2018-August/date.html

> On 7 May 2018, at 11:01, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Mon, May 7, 2018 at 5:52 AM, Brian Cain <brian.cain at gmail.com <mailto:brian.cain at gmail.com>> wrote: >> The simplest way to run a clang test case that I know of is to clone both >> llvm and clang repos, run all the tests, then run an individual test. >>

On Mon, May 7, 2018 at 5:52 AM, Brian Cain <brian.cain at gmail.com> wrote: > The simplest way to run a clang test case that I know of is to clone both > llvm and clang repos, run all the tests, then run an individual test. > > IIRC like so: > > git clone llvm ...... > cd llvm/tools > git clone clang ..... > cd ../../ > mkdir build > cd build > cmake

The simplest way to run a clang test case that I know of is to clone both llvm and clang repos, run all the tests, then run an individual test. IIRC like so: git clone llvm ...... cd llvm/tools git clone clang ..... cd ../../ mkdir build cd build cmake ../llvm ninja check-clang ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c On Sun, May 6, 2018 at 7:10 AM, Sedat Dilek via llvm-dev <

On Mon, May 7, 2018 at 5:19 PM, Brian Cain <brian.cain at gmail.com> wrote: > > > On Mon, May 7, 2018 at 10:13 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> >> ... > > >> >> sdi at iniza:~/src/llvm-toolchain/build$ ./bin/llvm-lit -v >> ./tools/clang/test/Sema/asm.c >> llvm-lit: >>

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

Hi Tom, I followed a bit the mailing-list but still see no LLVM v3.7.1 tarballs. Can you pleas take care of this? In case of that i386 breakage do a new v3.7.2 release, please. Not sure if this has impact on x86_64 (AMD64)? Thanks. Regards, - Sedat - [1] https://llvm.org/bugs/show_bug.cgi?id=25920

[ 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)? Helpful is to add

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" >

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: