search for: 3.4

On 10/04/2014 16:32, Tom Stellard wrote: > On Wed, Apr 09, 2014 at 06:47:19PM +0200, Sylvestre Ledru wrote: >> Hello, >> >> Trying the 3.4.1 branch, I get following tests failing: >> LLVM :: CodeGen/X86/2009-06-05-VZextByteShort.ll >> LLVM :: CodeGen/X86/fma4-intrinsics-x86_64.ll >> LLVM :: CodeGen/X86/fp-fast.ll >> LLVM ::

Hello, Trying the 3.4.1 branch, I get following tests failing: LLVM :: CodeGen/X86/2009-06-05-VZextByteShort.ll LLVM :: CodeGen/X86/fma4-intrinsics-x86_64.ll LLVM :: CodeGen/X86/fp-fast.ll LLVM :: CodeGen/X86/vec_shift4.ll LLVM :: CodeGen/X86/vshift-4.ll I am testing on a Debian testing 64b. Does it ring a bell? Sylvestre

In a pass I’m working on, I’ve done some manipulation of several functions, replacing them with new copies with different types, etc. The LLVM IR passes the verifier, but when I have debug symbols enabled (“-g”), I get the following error when Clang generates the Dwarf info (using a very recent build of LLVM/Clang from Git mirror): > Assertion failed: (TheCU && "Unable to find

On x86_64-apple-darwin12, I am seeing regressions in the current llvm 3.4 release branch during 'make check'... Scanning dependencies of target check-llvm [100%] Running the LLVM regression tests FAIL: LLVM :: CodeGen/Generic/isel-optnone.ll (1362 of 9265) ******************** TEST 'LLVM :: CodeGen/Generic/isel-optnone.ll' FAILED ******************** Script: --

Hi all, I use the nightly builds of LLVM in my Travis CI configuration. Travis CI is based on Ubuntu 12.04 precise. Currently, I am not able to install llvm-3.4 and llvm-3.4-dev. The error is always: $ sudo apt-get install llvm-3.4 llvm-3.4-dev Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package llvm-3.4 E: Couldn't find any

On Sun, Nov 10, 2013 at 06:11:16AM -0800, Bill Wendling wrote: > Good day! > > This is just a reminder that branching for the 3.4 release will occur at this time: > > Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November 19, 2013 at 3:00:00 AM UTC > > What this means for you! > ------------------------ > > * Please keep the release notes up to date --

Paul, could you take a look at this? Maybe it would make more sense for the in-progress optnone work to be omitted from the release? -- Sean Silva On Thu, Nov 21, 2013 at 11:27 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > On x86_64-apple-darwin12, I am seeing regressions in the current > llvm 3.4 release branch during 'make check'... > > Scanning

On Tue, Dec 3, 2013 at 9:04 PM, Brandon Holt <bholt at cs.washington.edu> wrote: > In a pass I’m working on, I’ve done some manipulation of several functions, replacing them with new copies with different types, etc. > > The LLVM IR passes the verifier, but when I have debug symbols enabled (“-g”), I get the following error when Clang generates the Dwarf info (using a very recent

Good day! This is just a reminder that branching for the 3.4 release will occur at this time: Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November 19, 2013 at 3:00:00 AM UTC What this means for you! ------------------------ * Please keep the release notes up to date -- There has been very few commits to them. Please be proactive and update them with any significant feature that was

I recently took a stab at changing the MacPorts llvm-3.4 port from the configure-based build system to the cmake-based build system. There are a couple of issues that I still haven't been able to work out yet and would like to know if these are just configuration issues on my side or bugs I should file at bugs.llvm.org: 1) libclang_rt It looks like the cmake build is missing some runtime

Thanks for the quick response. I wrote some code to search “llvm.dbg.cu” for the function (right before the failed assertion): if (TheCU == nullptr) { errs() << "compile unit: " << TheCU << "\n scopeNode(" << FnScope->getScopeNode() << ") => " << *FnScope->getScopeNode() << "\n"; auto fn =

When lld-3.4 is added to the tools directory of the llvm source tree as lld, the resulting cmake build produces a huge number of static libs and bloats the overall package from... -rw-r--r-- 1 root wheel 86361440 Nov 19 21:09 llvm34_3.4-0_darwin-x86_64.deb to -rw-r--r-- 1 root wheel 495257452 Nov 19 20:49 llvm34_3.4-0_darwin-x86_64.deb Is this a known issue with the initial release of

On Sun, Nov 10, 2013 at 7:50 PM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > On Sun, Nov 10, 2013 at 06:11:16AM -0800, Bill Wendling wrote: > > Good day! > > > > This is just a reminder that branching for the 3.4 release will occur at > this time: > > > > Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November > 19, 2013 at 3:00:00

Jack, Where do the "-isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk -mmacosx-version-min=10.8" flags come from? I don't see them in your CMake invocation - perhaps they're added via $CC or $CFLAGS? Is this being done on purpose? I can add a CMake step checking whether the current CFLAGS/LDFLAGS allow to build an

On Jul 24, 2013, at 11:11 AM, Jeremy Huddleston Sequoia wrote: > I recently took a stab at changing the MacPorts llvm-3.4 port from the configure-based build system to the cmake-based build system. > > There are a couple of issues that I still haven't been able to work out yet and would like to know if these are just configuration issues on my side or bugs I should file at

Hi everyone, I compiled grep with llvm-3.4(because consumer tool uses llvm3.4 bit code) and generate bit-code for this. When I am running with lli output is pseudo instructions should be removed before code emission UNREACHABLE executed at /home/awanish/llvm/llvm-3.4.2/lib/Target/X86/X86CodeEmitter.cpp:1176! 0 libLLVM-3.4.so 0x00007f1250f655d5 llvm::sys::PrintStackTrace(_IO_FILE*) + 37 1

Hi Jack, Are you packaging all the static libraries that lld produces as part of the package ? PS : When I build on x86_64, I only get a 9M image for lld. Thanks Shankar Easwaran On 11/20/2013 9:15 AM, Jack Howarth wrote: > When lld-3.4 is added to the tools directory of the llvm source tree > as lld, the resulting cmake build produces a huge number of static libs and > bloats

Dear R friends, I am currently using Windows 8, 64-bit operating system, x64-based processor. I have installed R version 3.4.1 "Single Candle". Also, I have several packages installed in this path: C:\Users\PaulBernal\Documents\R\win-library\3.4 Plus some other packages installed in this other path: C:\Users\PaulBernal\Desktop\DESTOP FILES\R Books C:\Users\PaulBernal\Desktop\DESTOP

This file is for configure+make build, not CMake, so I'm not sure why it's being included into your build (these failures aren't reproducible for me). Can you please list the exact steps you're doing to build LLVM with CMake and make sure you don't have additional CFLAGS (LDFLAGS etc) defined? On Mon, Nov 11, 2013 at 6:16 PM, Jack Howarth <howarth at bromo.med.uc.edu>

In your transform I'd take a look at things like the individual basic blocks you're replacing and the functions you're replacing and making sure that the various lexical blocks are being changed at the same time... -eric On Tue, Dec 3, 2013 at 11:12 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Tue, Dec 3, 2013 at 10:07 PM, Brandon Holt <bholt at