similar to: [LLVMdev] LLVM Rc3 sources?

The Asterisk.org development team is pleased to announced the release of Asterisk release candidates 1.6.0.7-rc2, 1.6.1.0-rc3, and beta release 1.6.2.0-beta1. Additionally, new release candidates of Asterisk-Addons 1.6.0.2-rc1 and 1.6.1.0-rc3 have been created. Note that the 1.6.1 series of Asterisk-Addons is compatible with both Asterisk 1.6.1 and 1.6.2 branches. These releases are available for

On 12/06/12 01:12, Pawel Wodnicki wrote: > Hello, > > Release Candidate 3 has been branched. > RC3 source code can be downloaded as tarballs from: > > http://llvm.org/pre-releases/3.2/rc3/ > > or directly from svn. > > Binaries will be posted shortly. > > Testing > > RC3 has a number of fixes related to MIPS support > that need to be well

2012/12/30 Larry Evans <cppljevans at suddenlink.net>: > I just created clang with the tarballs without problem; however, > when `make check-all` was run, I got 1 error. My system is: > ~/download/llvm/pre-releases/3.2/rc3/download/build_debug $ make check-all > llvm[0]: Running test suite > make[1]: Entering directory >

On Sun, Dec 30, 2012 at 1:58 AM, Larry Evans <cppljevans at suddenlink.net>wrote: > On 12/29/12 18:40, NAKAMURA Takumi wrote: > > 2012/12/30 Larry Evans <cppljevans at suddenlink.net>: > >> I just created clang with the tarballs without problem; however, > >> when `make check-all` was run, I got 1 error. My system is: > > > >>

On Wed, Mar 9, 2016 at 10:30 PM, Sylvestre Ledru via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Le 09/03/2016 à 21:44, Yury V. Zaytsev a écrit : > > On Wed, 9 Mar 2016, Sylvestre Ledru wrote: > > > >> This is still maintained. However the cmake transition (for both 3.8 > >> and 3.9) wasn't simple... While it should be fine for debian, it >

On Wed, 9 Mar 2016, Sylvestre Ledru wrote: > This is still maintained. However the cmake transition (for both 3.8 and > 3.9) wasn't simple... While it should be fine for debian, it might need > more work for old Ubuntu (back port of cmake) Hi Sylvestre, Thank you for the clarification! Any ETAs on when the APT repositories are going to be updated with LLVM 3.8 & 3.9 builds?

Hi, I had a quick look at that link and it seems to be a linker internal error. Presumably we're triggering a bug in the system toolchain. FWIW, my mipsel build on a Debian Jessie machine (binutils 2.24.90.20141023-1) successfully completed test-release.sh. I'm currently running the tests. Here's the relevant bit of the log from your link: cd

> Test suite is green but I'm seeing two libc++ test failures when running check-all. What tests are failing? On Fri, Jun 10, 2016 at 5:13 PM, Nikola Smiljanic via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Uploaded Fedora and openSUSE binaries. Test suite is green but I'm seeing > two libc++ test failures when running check-all. I'm pretty sure these were >

Hello, Release Candidate 3 has been branched. RC3 source code can be downloaded as tarballs from: http://llvm.org/pre-releases/3.2/rc3/ or directly from svn. Binaries will be posted shortly. Testing RC3 has a number of fixes related to MIPS support that need to be well exercised. Otherwise, I think we are at the point of the release where I can *challenge* testers to try to break it!

Hi, I just tagged LLVM 4.0.1-rc3, and it's ready for testing. If all goes well, we will do the final release on Monday. -Tom

Hello testers, Start your engines, RC3 has just been tagged (at r229050 on the branch). If this one looks good, it will become the release. There has been quite a bit of activity on the branch since RC2; let's hope it's all goodness :-) Please let me know how it looks, and upload binaries to the sftp as usual. Thanks for all your efforts so far! - Hans

On 06/06/2013 18:04, Hans Wennborg wrote:> It's probably PR12517. > > Looking at the clang binary, it's got a /home/ dir in RPATH: > > $ objdump -p clang+llvm-3.3rc3-Ubuntu-12.04.2-x86_64/bin/clang | grep RPATH > RPATH > $ORIGIN/../lib:/home/aadgrand/tmp/LLVM-3.3rc3/rc3/Phase3/Release+Asserts/llvmCore-3.3-rc3.obj/Release+Asserts/bin To avoid such behavior [1] , in

Le 12/03/2016 à 14:15, Johan Engelen a écrit : > > > > I'm not sure how clean / dirty of a solution you'd be okay with, but > > I'd just point out that CMake developers provide working binary > > tarballs for Linux with every release at > https://cmake.org/download/ . > > So, if you are not a purist and/or need the CMake backport for

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

Quick update before I move on to the final tag. > clang+llvm-3.6.0-rc4-mipsel-linux-gnu.tar.xz > Still running due to a silly setup mistake on the first run (a broken > symlink to the test-suite source). Second attempt is a fair way through and > looks good so far though Default options were all good. Mips32 was about halfway but was good so far. >

Subject: How to define vector element type bool in builtin function hello everyone,I have defined intrinsic function like this: def int_mips_add_32 : GCCBuiltin<"__builtin_dongxin_add_32">, Intrinsic<[llvm_v4i32_ty], [llvm_v4i32_ty, llvm_v4i32_ty,llvm_v8i1_ty]>; Then I write a test code : typedef int v4i32 __attribute__ ((vector_size(16))); typedef bool v8i1

> 32bitmicro <root at 32bitmicro.com> writes: >> - Release Candidate 3 (RC3) >> >> RC3 will be created on Wednesday Dec 5th 10 p.m. PST. Please let me >> know if there are any patches for release stopping issues that should >> be included in the RC3. > > Is the fix for 14465 important enough for the 3.2 release? It's an ICE > that I hit in RC1

Approved. Sorry for the delay. On Mon, Dec 3, 2012 at 8:27 PM, 32bitmicro <root at 32bitmicro.com> wrote: > > > 32bitmicro <root at 32bitmicro.com> writes: > >> - Release Candidate 3 (RC3) > >> > >> RC3 will be created on Wednesday Dec 5th 10 p.m. PST. Please let me > >> know if there are any patches for release stopping issues that

32bitmicro <root at 32bitmicro.com> writes: > - Release Candidate 3 (RC3) > > RC3 will be created on Wednesday Dec 5th 10 p.m. PST. Please let me > know if there are any patches for release stopping issues that should > be included in the RC3. Is the fix for 14465 important enough for the 3.2 release? It's an ICE that I hit in RC1 that's still there in RC2. Benjamin

Are we waiting for an RC5? It seems like the release mirror on github has no recent activity. On Wed, Feb 25, 2015 at 3:23 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Quick update before I move on to the final tag. > > > clang+llvm-3.6.0-rc4-mipsel-linux-gnu.tar.xz > > Still running due to a silly setup mistake on the first run (a > broken >