search for: release_30

I downloaded via svn the release_30 and current version code. I am on x86_64 GNU/Linux, I am compiling with gcc 4.4.6 I compiled release_30 with make ENABLE_OPTIMIZED=0 OPTIMIZE_OPTION=-O0 and current release with make In both cases, when I make check-all I get : FAIL: Clang :: Preprocessor/macro_paste_c_block_comment.c (...

I downloaded via svn the release_30 and current version code. I am on x86_64 GNU/Linux, I am compiling with gcc 4.4.6 I compiled release_30 with make ENABLE_OPTIMIZED=0 OPTIMIZE_OPTION=-O0 and current release with make In both cases, when I make check-all I get : FAIL: Clang :: Preprocessor/macro_paste_c_block_comment.c (2...

Hi Simona, these failures are due to the name of the path to LLVM/clang, see below. > /scratch/user/download/release_30/build/Debug/bin/clang -cc1 -internal-isystem > /scratch/user/download/release_30/build/Debug/bin/../lib/clang/3.0/include > /scratch/user/download/release_30/llvm/tools/clang/test/Preprocessor/macro_paste_c_block_comment.c > > > -Eonly 2>&1 | not grep scratch This test checks...

It can pass on trunk. http://bb.pgr.jp/builders/clang-ppc-linux/builds/91/steps/test_llvm/logs/stdio Note: You still need to add -UPPC on configure or make. Clang tests will not let passed for me. There might be many issues. It fails on some point on release_30. r143303 in release_30 http://bb.pgr.jp/builders/clang-ppc-linux/builds/92/steps/test_llvm/logs/stdio Failing Tests (5): * LLVM :: CodeGen/X86/dbg-i128-const.ll Fixed in r143194. I think it might be partial fix. It was endianness issue on MC Dwarf. * LLVM :: MC/AsmParser/2011-09-06-NoNewlin...

The LLVM 3.0 release branch has been tagged. You may now commit patches at your leisure. Thank you for keeping the ToT healthy! -bw

On 10/15/2011 05:02 AM, Bill Wendling wrote: > The LLVM 3.0 release branch has been tagged. You may now commit patches at your leisure. Could we have a release_30 branch in git tracking the SVN release_30 branch? Thanks, --Edwin

> Could we have a release_30 branch in git tracking the SVN release_30 branch? Added for {llvm,clang,compiler-rt,dragonegg}.git Let me know if I missed something :) -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hi, I compiled llvm v3.0 on linux x86_64 with gcc 4.4.6 and test-suite fails on two tests: SingleSource/UnitTests/Vector/SSE/sse.expandfft SingleSource/UnitTests/Vector/SSE/sse.stepfft I configured and compiled with with ../llvm/configure CFLAGS=-O3 --prefix=/scratch/user/local/llvm-release_30_opt --enable-optimized make -j2 make check-all and tested with gmake TEST=simple report report.html I got two failures, which flags should I use to compile with optimization but avoiding these errors? ========= '/scratch/user/download/release_30/build_optimized/projects/te...

...ate] release_25 -> llvm.org/release_25 = [up to date] release_26 -> llvm.org/release_26 = [up to date] release_27 -> llvm.org/release_27 = [up to date] release_28 -> llvm.org/release_28 = [up to date] release_29 -> llvm.org/release_29 = [up to date] release_30 -> llvm.org/release_30 = [up to date] release_31 -> llvm.org/release_31 = [up to date] release_32 -> llvm.org/release_32 = [up to date] release_33 -> llvm.org/release_33 = [up to date] release_34 -> llvm.org/release_34 = [up to date] release_35 -> llv...

Anton Korobeynikov <anton at korobeynikov.info> writes: >> Could we have a release_30 branch in git tracking the SVN release_30 branch? > Added for {llvm,clang,compiler-rt,dragonegg}.git Let me know if I > missed something :) Do we branch the test suite? Err...do we even have a test suite git mirror? -Dave

Hi All , Was trying to build the LLVM src from http://llvm.org/svn/llvm-project/llvm/branches/release_30 ,But unable to build the same and clang poped up with below error . llvm[1]: Compiling IntervalMap.cpp for Debug build In file included from /root/projects/safecode/llvm/lib/Support/IntervalMap.cpp:14: /root/projects/safecode/llvm/include/llvm/ADT/IntervalMap.h:1980:32: error: use 'template...

...; llvm.org/release_25 > = [up to date] release_26 -> llvm.org/release_26 > = [up to date] release_27 -> llvm.org/release_27 > = [up to date] release_28 -> llvm.org/release_28 > = [up to date] release_29 -> llvm.org/release_29 > = [up to date] release_30 -> llvm.org/release_30 > = [up to date] release_31 -> llvm.org/release_31 > = [up to date] release_32 -> llvm.org/release_32 > = [up to date] release_33 -> llvm.org/release_33 > = [up to date] release_34 -> llvm.org/release_34 > = [up to date]...

...(outs GPR:$dst), (ins GPR:$ptr, GPR:$val), NoItinerary, [(set GPR:$dst, (atomic_load_min_32 GPR:$ptr, GPR:$val))]>; both reference atomic_load_min_32, and the latter should instead reference atomic_load_umin_32 Added here, See http://llvm.org/viewvc/llvm-project/llvm/tags/RELEASE_30/final/lib/Target/ARM/ARMInstrInfo.td?diff_format=h&view=diff&r1=130233&r2=130234 Still present in trunk http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Target/ARM/ARMInstrInfo.td?diff_format=h&view=annotate Cheers, George

...are selectively folded into the release branch until the release is blessed, and then (generally speaking) the release branch isn't touched again. SAFECode works differently. With SAFECode, there is a release_xx branch for each release of LLVM that we support. For example, the SAFECode release_30 branch works with the release_30 branch of LLVM. The idea is to make it easy for people to grab updates to SAFECode that work with a particular LLVM version. The real difference is that SAFECode usually sticks with a single release of LLVM for awhile, so while LLVM is developed on trunk, we o...

...o msys build. I guess msysdtk would have it. > Otherwise, I tried the above building process with the trunk version of > LLVM, but to no avail. Maybe this will be possible with the forthcoming LLVM > 3.0…? Anyway, any help on the above would be much appreciated… AFAIK, on msys, trunk and release_30 is almost fine. http://bb.pgr.jp/builders/clang-i686-msys Though, here is no builder on win32 with --enable-shared. ps. you might need also --enable-optimized --enable-shared --enable-embed-stdcxx HTH, ...Takumi

On Mon, May 14, 2012 at 4:39 PM, John Criswell <criswell at illinois.edu>wrote: > On 5/14/12 4:32 AM, Umesh Kalappa wrote: > > Hi All , > > Was trying to build the LLVM src from > http://llvm.org/svn/llvm-project/llvm/branches/release_30 ,But unable to > build the same and clang poped up with below error . > > > First, it sounds like you're building LLVM 3.0, Poolalloc, and SAFECode > with an unmodified version of clang. Is this correct? If so, which > version of Clang are you using? > > Second, what p...

...$val), NoItinerary, > [(set GPR:$dst, (atomic_load_min_32 GPR:$ptr, GPR:$val))]>; > > both reference atomic_load_min_32, and the latter should instead > reference atomic_load_umin_32 > > Added here, > See > http://llvm.org/viewvc/llvm-project/llvm/tags/RELEASE_30/final/lib/Target/ARM/ARMInstrInfo.td?diff_format=h&view=diff&r1=130233&r2=130234 > > Still present in trunk > http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Target/ARM/ARMInstrInfo.td?diff_format=h&view=annotate > > Cheers, > George > _____________________...

> Was trying to build the LLVM src from http://llvm.org/svn/llvm-project/llvm/ > branches/release_30 ,But unable to build the same and clang poped up with below > error . Are you bulidling LLVM trunk or branch 3.0? Or you can try LLVM 3.1 release, which will be released soon. Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Tai...

Hi Anton, It seems that some release branches (e.g. release_30, release_35, and release_36) are missing from the Git mirror for libc++abi. May you help to fix the problem? Thanks. Sincerely, Logan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150201/68faf5d4/attachm...

...[(set GPR:$dst, (atomic_load_min_32 GPR:$ptr, GPR:$val))]>; >> >> both reference atomic_load_min_32, and the latter should instead >> reference atomic_load_umin_32 >> >> Added here, >> See >> http://llvm.org/viewvc/llvm-project/llvm/tags/RELEASE_30/final/lib/Target/ARM/ARMInstrInfo.td?diff_format=h&view=diff&r1=130233&r2=130234 >> >> Still present in trunk >> http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Target/ARM/ARMInstrInfo.td?diff_format=h&view=annotate >> >> Cheers, >> George >...