search for: release_33

...ate] 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 -> llvm.org/release_35 = [up to date] release_35 at 215010 -> llvm.org/release_35 at 215010 = [up to date] release_36 -> llvm.org/release_36 = [up to date]...

...; 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 -> llvm.org/release_35 > = [up to date] release_35 at 215010 -> llvm.org/release_35 at 215010 > = [up to date] release_36 -> llvm.org/release_36 &...

LLVM builds with me on the release_33 branch, but fails on trunk. I bisected the problem to this commit: commit b49fb7bcd5001567d2da06f6a6e1c7ba79649e1b Author: Daniel Dunbar <daniel at zuster.org> Date: Wed Aug 14 23:15:39 2013 +0000 [llvm-build] Make Py3 compatible. git-svn-id: https://llvm.org/svn/llvm-project/ll...

...lt;Value *>(&Ops[0], 2), "palignr"); And clang v3.9 migrated X86::BI__builtin_ia32_palignr128 like this https://github.com/llvm-mirror/clang/blob/master/lib/CodeGen/CGBuiltin.cpp#L7629 just ignored the if (shiftVal < 32) condition? https://github.com/llvm-mirror/clang/blob/release_33/lib/CodeGen/CGBuiltin.cpp#L2642 Please give me some hint, thanks a lot! -- Regards, Leslie Zhai - a LLVM developer https://reviews.llvm.org/p/xiangzhai/

...'ve traced it to a bug in configparser, which on my python 2.7.4 system is a backport of configparser from python 3. Here is a clean patch that works around the problem. Geoffrey On Wed, Nov 6, 2013 at 10:24 AM, Geoffrey Irving <irving at naml.us> wrote: > LLVM builds with me on the release_33 branch, but fails on trunk. I > bisected the problem to this commit: > > commit b49fb7bcd5001567d2da06f6a6e1c7ba79649e1b > Author: Daniel Dunbar <daniel at zuster.org> > Date: Wed Aug 14 23:15:39 2013 +0000 > > [llvm-build] Make Py3 compatible. > > git-sv...

I'm attempting to build 3.3 with clang included (by checking out clang branches/release_33 to the tools/clang directory). When I run configure I get this error: config.status: creating docs/doxygen.cfg config.status: error: cannot find input file: ./tools/clang/docs/doxygen.cfg.in Even if I "--enable-doxygen=no --enable-docs=no" I still get this error. Attempting to remove th...

I have simple standalone ASan examples working on Android, and now I'd like to try using ASan with the Android build system. I'm building the release_33 branch of llvm+clang+compiler-rt with CMake. To test, I'm looking at libjpg, because with just a small change its Android.mk it compiles in a few seconds and without needing any additional dependencies. When I run 'djpeg' on JellyBean, ASan reports the error message below. Can you pl...

> const uptr kThreadDescriptorSize = FIRST_32_SECOND_64(1168, 2304); Yes, that change causes all tests to pass. > I need to figure out which ifdefs to put this under, so I might not be able to land the fix until Monday. Okay, no worries, thanks for doing this. I've moved over to release_33 for the short-term. With the one change mentioned earlier (#include <stdint.h>), asan is working well for me when targeting either X86 Linux or ARM Android. -Greg On Fri, May 31, 2013 at 11:50 AM, Sergey Matveev <earthdok at google.com> wrote: > As a temporary fix, you can replace...

...VERSION=clang3.3 APP_PLATFORM=android-8 -Greg On Tue, Jun 4, 2013 at 11:21 AM, Greg Fitzgerald <garious at gmail.com> wrote: > I have simple standalone ASan examples working on Android, and now I'd > like to try using ASan with the Android build system. I'm building > the release_33 branch of llvm+clang+compiler-rt with CMake. To test, > I'm looking at libjpg, because with just a small change its Android.mk > it compiles in a few seconds and without needing any additional > dependencies. > > When I run 'djpeg' on JellyBean, ASan reports the error me...

> What version of glibc are you building with on x86? 2.11.1 for 64-bit x86 linux $ ldd --version ldd (Ubuntu EGLIBC 2.11.1-0ubuntu7.8) 2.11.1 On Fri, May 31, 2013 at 8:24 AM, Sergey Matveev <earthdok at google.com> wrote: > Those changes shouldn't affect ARM at all, since everything is under #if > defined(__i386__) || defined(__x86_64__). > > What version of glibc are

...l/vendor/toolchains/llvm/3.3/armv7m/bin/armv7m-none-eabi-clang -mcpu=cortex-m4 -mfloat-abi=soft -mthumb -nostdinc -ffreestanding -ffunction-sections -fdata-sections -fno-exceptions -fno-rtti -fomit-frame-pointer -momit-leaf-frame-pointer -nostdinc -v -Os -S -o a.s a.c vendor-clang version 3.3 (tags/RELEASE_33/final) (based on LLVM 3.3) Target: armv7m-none--eabi Thread model: posix "/usr/local/vendor-20130805-b8d59d2/toolchains/llvm/3.3/armv7m/bin/armv7m-none-eabi-clang" -cc1 -triple thumbv7em-none--eabi -S -disable-free -main-file-name a.c -mrelocation-model static -fmath-errno -mconstructor-...

...my very first testing session, but I think that I've figured it out ... at least the procedure makes sense to me ;) The full procedure for getting the nightly test results of *a single RC* is as follows: 1. Get the sources for LLVM + Clang from SVN (i.e. checkout from the specific tags, e.g. RELEASE_33/rc1) 2. Run the script from utils/release/test-release.sh with appropriate arguments, e.g. to build 3.3 RC1: test-release.sh -release 3.3 -rc 1 Adapt -build-dir and -j as needed 3. Once 2 is finished, download the llvm-test-suite, install LNT (if not done already) and run it, don't forg...

...ust not removed correctly? > > > > Thanks, > > Tobias > > Tobias, > I still see test/Isl/CodeGen/scevcodegen-1.ll in the polly 3.3 release branch (svn). > It is also shown to still be present by the urls... > > http://llvm.org/svn/llvm-project/polly/branches/release_33/test/Isl/CodeGen/scevcodegen-1.ll > > but does seem to be removed in trunk... > > http://llvm.org/svn/llvm-project/polly/trunk/test/Isl/CodeGen/ > > Can we get those changes into the polly 3.3 release tarball? > Jack > Tobias, I can also confirm that the cha...

Those changes shouldn't affect ARM at all, since everything is under #if defined(__i386__) || defined(__x86_64__). What version of glibc are you building with on x86? On Fri, May 31, 2013 at 7:16 PM, Greg Fitzgerald <garious at gmail.com> wrote: > The failures happen on x86 Linux, Ubuntu Lucid. On ARM Android, my > example code segfaults, whereas before it worked. I

As a temporary fix, you can replace this line in sanitizer_linux_libcdep.c: const uptr kThreadDescriptorSize = FIRST_32_SECOND_64(1216, 2304); with const uptr kThreadDescriptorSize = FIRST_32_SECOND_64(1168, 2304); The tests should pass after that. I need to figure out which ifdefs to put this under, so I might not be able to land the fix until Monday. On Fri, May 31, 2013 at 8:48 PM, Greg

Hi guys, I am trying to perform edge profiling using on hello.bc file by using following command opt -insert-edge-profiling hello.bc -o hello-edge.bc but I get the error that option "-insert-edge-profiling" is unknown. Can you please help me to solve the issue. Please note that I am following the paper available at this link http://llvm.org/pubs/2010-12-Preuss-PathProfiling.pdf

...3.3 on Linux and used -pg and -O2 option. The program would crash with segfault. Interestingly if I compile it with -pg option only it works. Do you have any idea why it crashes? And any workaround? $ cat myprog.c int main() { return 0; } $ clang -v -pg -O2 myprog.c clang version 3.3 (tags/RELEASE_33/final) Target: x86_64-pc-linux-gnu Thread model: posix "/usr/bin/clang" -cc1 -triple x86_64-pc-linux-gnu -emit-obj -disable-free -disable-llvm-verifier -main-file-name myprog.c -mrelocation-model static -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -ta...

...3.3/armv7m/bin/armv7m-none-eabi-clang > -mcpu=cortex-m4 -mfloat-abi=soft -mthumb -nostdinc -ffreestanding > -ffunction-sections -fdata-sections -fno-exceptions -fno-rtti > -fomit-frame-pointer -momit-leaf-frame-pointer -nostdinc -v -Os -S -o > a.s a.c > vendor-clang version 3.3 (tags/RELEASE_33/final) (based on LLVM 3.3) > Target: armv7m-none--eabi > Thread model: posix > "/usr/local/vendor-20130805-b8d59d2/toolchains/llvm/3.3/armv7m/bin/armv7m-none-eabi-clang" > -cc1 -triple thumbv7em-none--eabi -S -disable-free -main-file-name a.c > -mrelocation-model static -f...

...eck if this is a stale > file that was just not removed correctly? > > Thanks, > Tobias Tobias, I still see test/Isl/CodeGen/scevcodegen-1.ll in the polly 3.3 release branch (svn). It is also shown to still be present by the urls... http://llvm.org/svn/llvm-project/polly/branches/release_33/test/Isl/CodeGen/scevcodegen-1.ll but does seem to be removed in trunk... http://llvm.org/svn/llvm-project/polly/trunk/test/Isl/CodeGen/ Can we get those changes into the polly 3.3 release tarball? Jack

First, let me ask if there's a page that documents the testing process in full. If there is, just give me a link to that and save yourself the time of answering this. (I did Google it, all I found was docs on writing tests for LLVM.) Sorry if this is way off, but I have no idea what to download and unpack to start testing. I know it's stuff from here: