search for: release_380

On 2 June 2016 at 19:50, Richard Gomes via llvm-dev <llvm-dev at lists.llvm.org > wrote: > Since the APT repository is down... everything under that location is > unavailable, including the instructions on how I could build/install > LLVM/clang from sources. Could you guys advise, please? > You can quickly start here... http://clang.llvm.org/get_started.html at least until we

..., b2+1, 16)); Why is the file failing to compile? ========== Here are some details of the host: Operating System Details Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial ... OS/Arch: linux/ppc64le clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final) ========== Compile is OK on my old PowerMac G5, GCC112 and GCC119 from the compile farm. Unfortunately, the compile farm only tests GCC and XLC. The Clang compiler does not work. Thanks in advance. Jeff

[ 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 several files from my project (ISPC, https://github.com/ispc/ispc). I've reproduced this on MacOS and Linux. Please let me know if you need any other info. How to reproduce: 1) Build address sanitized clang 3.8rc1: cd /path-to-working-dir svn co http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_380/rc1/ llvm cd llvm/tools svn co http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_380/rc1/ clang cd clang/tools svn co http://llvm.org/svn/llvm-project/clang-tools-extra/tags/RELEASE_380/rc1/ extra cd ../../../projects svn co http://llvm.org/svn/llvm-project/compiler-rt/tags/RELEASE_380/rc1/ compile...

...ppa <umesh.kalappa0 at gmail.com> wrote: > Hi All , > > We are looking at the C sample i.e > > extern int i,j; > > int test() > { > while(1) > { i++; > j=20; > } > return 0; > } > > command used :(clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final) > ) > clang -S test.c -O2 > > the generated asm for x86 > > .L2: > jmp .L2 > > we understand that,the infinite loop is not deterministic ,compiler > is free to treat as that as UB and do aggressive optimization ,but we > need keep the side effect...

...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/Cl...

..."target-cpu"="x86-64" "target-features"="+fxsr,+mmx,+sse,+sse2" "unsafe-fp-math"="false" "use-soft-float"="false" } attributes #1 = { nounwind } !llvm.ident = !{!0} !0 = !{!"clang version 3.8.0 (tags/RELEASE_380/final)"} When I run the pass on the bitcode: `opt -load hello/libhello.so -hello src/world.bc > /dev/null`, the output is: Hello: main However, the [tutorial][2] claims that the output should have been: Hello: __main Hello: puts Hello: main Why does my pass not get trig...

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 Thu, Oct 24, 2019 at 2:22 PM Jinsong Ji <jji at us.ibm.com> wrote: > Looks like to me that your clang is too old. > > clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final) > > clang 3.8.0 was released on 08 Mar 2016. > > While vec_xl was added in https://reviews.llvm.org/rL286455 onNov 11 > 2016, which is around half an year later then 3.8.0. > > Can you please try using newer clang. > Thanks. Travis does not allow an upgrade of the co...

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

...file has only 3156 bytes size 2. and in disassembler only main function 3. the final executable will be 49992 bytes size in this case But compilation in llvm's clang downloaded from http://llvm.org/releases/3.8.0/clang+llvm-3.8.0-x86_64-apple-darwin.tar.xz ( clang version 3.8.0 (tags/RELEASE_380/final) Target: x86_64-apple-darwin15.0.0 Thread model: posix ) gives another results: 1. object file has 159044 bytes size 2. in disassembler a lot of unnecessary .objc_property_list, .objc_method_list, .objc_protocol_list and .objc_protocol  in .bss and .data section...

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

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

...ually the LTO pipeline is a bit different from what you're doing, I'm used to see: $clang -flto -O3 -c main.c -o main.o $clang -flto -O3 -c a.c -o a.o $clang -flto -O3 main.o a.o -o main0 -- Mehdi > > $ clang -O2 -flto main.lib a.lib -o main2 -v > clang version 3.8.0 (tags/RELEASE_380/final) > Target: x86_64-unknown-linux-gnu > Thread model: posix > InstalledDir: /usr/local/bin > Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9 > Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.3 > Found candidate GCC installation: /usr/lib...

...e.o --- zlib/inflate.c:1528:61: warning: shifting a negative signed value is undefined [-Wshift-negative-value] if (strm == Z_NULL || strm->state == Z_NULL) return -1L << 16; ~~~ ^ # cc --version FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) Target: x86_64-unknown-freebsd11.0 Thread model: posix Thx ! Ben -- You are receiving this mail because: You are the QA Contact for the bug.

> Try checking out libcxxabi as well. It helped, thanks. But I have another problem now. Regression tests don't pass: http://paste.ubuntu.com/15406485/ Also I discovered that build process sometimes consumes about 10 Gb of RAM. Luckily I have total 16 Gb of RAM. Still I had to close Google Chrome and kill KVM guest systems to compile a project. I think its just an insanity. -- Best

Hi All , We are looking at the C sample i.e extern int i,j; int test() { while(1) { i++; j=20; } return 0; } command used :(clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final) ) clang -S test.c -O2 the generated asm for x86 .L2: jmp .L2 we understand that,the infinite loop is not deterministic ,compiler is free to treat as that as UB and do aggressive optimization ,but we need keep the side effects like j=20 untouched by optimization . Please note...

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

Hi Umesh, Thank you for the suggestion. I can use the "Brute force method " to narrow down the LTO wrong instructions here and there, but I still don't know why these wrong instructions are generated, and how to let Clang LTO don't generate those wrong instructions. I suspect the wrong code is caused by some LTO wrong optimization pass, so I hope to disable all optimizations in

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