search for: release_35

...ate] 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] release_37 -> llvm.org/release_37 = [up to date] release_38 -> llvm.org/release_38 = [up to date]...

> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: > > That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. > It can be deleted now, if anyone wants to. ``` $ git push llvm.org :release_35 at 215010 fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested URL returned error: 403 ``` Who has access to this? > Doesn't really seem like it matters though. Not important, surely, but we might as well clean it up! > > On Fri, Feb 5, 2016 at 5:34 PM,...

Hello, disclaimer/ Apologies if this is the wrong llvm/clang mailing list; please, direct me to the right one if needed. /disclaimer I've been experiencing issues with incomplete type info when debugging code generated by clang 3.5.0 from the recent release_35 branch. Generally, the problem manifests itself as the inability to examine any std::string parameter to a function, in either gdb or lldb: (lldb) p arg_string (std::string) $4 = error: summary string parsing error (gdb) p arg_string $2 = (const std::string &) @0x7fffffffd948: <incomplete...

Hello, I've stumbled upon the following behavior in branches/release_35 (as of 218689) under ubuntu 14.04 LTS amd64: whenever I include the (system-wise) gnu iostream header, clang++ stops devirtualizing the following code: #if BREAKAGE_ENSUES #include <iostream> #endif struct Base { virtual int foo() const = 0; }; struct A : Base { int a; A(const int a) : a...

...that they don't depend on my other work. If you have any questions there or need me to stamp the rewrites as "what should happen if you don't take my patches into account" I'm happy to do so. > > Thanks. > > -eric I believe I've managed to backport them to the release_35 branch but I haven't re-tested them beyond running 'ninja check-all' yet. The patches are currently at https://github.com/dsandersimgtec/clang/commits/release_35, and https://github.com/dsandersimgtec/llvm/commits/release_35_proposed. I'm going to run as much ABI testing as possibl...

...the way CMake files are generated by the Autoconf/Makefile system and fixed this in r217484. I figured it would be more sensible to ask about this in a thread separate from [2] because this is a much more general question. So what should I do here? Should I also commit this patch to the branches/release_35 or am I not allowed to do this and instead should downstream (e.g. Debian, Arch.. etc) just apply the patch when building their packages? Even if I add the patch to the release branch I don't think most distributions will get it because they'll probably use the tarballs which won't hav...

On 09/09/2014 01:53 PM, Dan Liew wrote: >> It looks like LLVMConfigLibs was created in r112714 for local use in >> Makefile.rules. The only use outside Makefile.rules is now in >> cmake/modules/Makefile. Teaching cmake/modules/Makefile to do >> a direct invocation would be fine with me. > > Okay. Attached is a patch that does this. Does this work okay for you?

On 13 December 2014 at 16:50, Renato Golin <renato.golin at linaro.org> wrote: > Same here... ARMv7 is already up and tested, AArch64 is proving a bit > more complicated due to old libstdc++ on my box. I'm working on it. I'm seeing one error on AArch64's test-suite: SingleSource/UnitTests/Vector/AArch64/aarch64_neon_intrinsics.c:154979:16: warning: implicit declaration of

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/attachment.html>

...enable-shared \ --enable-targets=all \ --disable-expensive-checks \ --disable-debug-runtime \ --disable-assertions \ --with-binutils-include=/usr/include \ --enable-optimized Is it possible to map this to cmake flags and if yes how? Platform is linux-x86_64 and revision is release_35 branch. If there's superfluous flags please do tell and I'll remove them. Also is there a flag to skip tests? Is building lld on linux supported? I tried including lld in the build and it failed: llvm[4]: Linking Release unit test CoreTest (without symbols) /tmp/llvm/build/Release/lib/li...

...e or need me to stamp the rewrites as "what should happen if you don't take my patches into account" I'm > > > happy to do so. > > > > > > Thanks. > > > > > > -eric > > > > I believe I've managed to backport them to the release_35 branch but I haven't re-tested them beyond running > > 'ninja check-all' yet. The patches are currently at https://github.com/dsandersimgtec/clang/commits/release_35, > > and https://github.com/dsandersimgtec/llvm/commits/release_35_proposed. > > I'm going to run...

Hi all, I can't seem to get the simplest CMakeLists.txt file working from http://llvm.org/docs/CMake.html#embedding-llvm-in-your-project. Do any of the LLVM projects use `find_package(LLVM REQUIRED CONFIG)`? Should I just be using `llvm-config` directly? http://llvm.org/bugs/show_bug.cgi?id=20884 David

...> --disable-expensive-checks \ > --disable-debug-runtime \ > --disable-assertions \ > --with-binutils-include=/usr/include \ > --enable-optimized > > Is it possible to map this to cmake flags and if yes how? > > Platform is linux-x86_64 and revision is release_35 branch. > > If there's superfluous flags please do tell and I'll remove them. > > Also is there a flag to skip tests? > > Is building lld on linux supported? I tried including lld in the build and it failed: > llvm[4]: Linking Release unit test CoreTest (without symbols...

> -----Original Message----- > From: Tom Stellard [mailto:tom at stellard.net] > Sent: 24 November 2014 17:15 > To: Daniel Sanders > Cc: LLVM Developers Mailing List (llvmdev at cs.uiuc.edu) > Subject: Re: Proposed patches for Clang 3.5.1 > > On Mon, Nov 24, 2014 at 04:33:28PM +0000, Daniel Sanders wrote: > > Hi, > > > > I'd like to propose the

Hi Martin, On Fri, 3 Aug 2018 at 14:10, Martin J. O'Riordan <MartinO at theheart.ie> wrote: > $ git branch --list > * master > martino By default "git branch" only lists local branches. "git branch -a" will list all of them, including (for me) "remotes/origin/release_70". If you just type "git checkout release_70" git will

...I have a simple example project that uses ``find_package(LLVM)``. Here are the steps I followed to build (I build against the LLVM build directory and don't bother installing it) $ mkdir tutorial/ # Build LLVM $ mkdir llvm/ $ cd llvm/ $ svn co http://llvm.org/svn/llvm-project/llvm/branches/release_35 src $ mkdir build $ cd build $ cmake -G Ninja ../src $ ninja # This is just for convenience when setting LLVM_DIR later on. $ LLVM_BUILD_ROOT="$(pwd)" # Build simple tutorial project $ cd ../ $ mkdir srg-llvm-pass-tutorial $ git clone https://github.com/delcypher/srg-llvm-pass-tutorial.g...