search for: rdivacki

Hi, My New Year's resolution is to complain (constructively) whenever I get a spurious build failure email from a buildbot. For new or infrequent contributors especially, they can be extremely confusing and unnecessarily alarming. This one below is the first build ever attempted by the builder, so how on earth can it have come up with a meaningful blame list? And in any case, surely we

Hi, Target overrides of processFunctionBeforeFrameFinalized() are misused in two cases (MBlaze and PowerPC) to set the offsets of objects. Unfortunately this has no effect because the offsets are immediately reset by calculateFrameObjectOffsets(). The PowerPC backend does this to setup the stack frame layout according to the ABI. Ie. it spills the registers etc. in a fixed layout. How to do

Guys, you can exclude me (dyatkovskiy) from this list, since I reverted my changes in r162354. -Stepan. llvm.buildmaster at lab.llvm.org wrote: > The Buildbot has detected a new failure on builder clang-native-mingw64-win7 while building cfe. > Full details are available at: > http://lab.llvm.org:8011/builders/clang-native-mingw64-win7/builds/876 > > Buildbot URL:

This builder is taking too long to build. (The build stops because of a timeout.) Chip On Aug 30, 2013, at 11:29 AM, llvm.buildmaster at lab.llvm.org wrote: > The Buildbot has detected a new failure on builder clang-amd64-openbsd while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/clang-amd64-openbsd/builds/1103 > > Buildbot URL:

Hi! I am trying to implement va_arg() on ppc32. Everything went smooth, except implementing va_arg() of 64bit int. Since i64 is not a legal type on ppc32 DAGTypeLegalizer::ExpandRes_VAARG() splits the va_arg(i64) into two i32 va_args. The problem with ppc32 va_arg is that it needs special "alignment" of its gpr pointer when the argument is i64. Ie. I need to know if I am lowering

Hi, In FreeBSD, we aim for replacing gcc with clang. We can compile all of the base system except the loader which does not fit within the hardware limits (7680 bytes). Currently (r127066) clang/llvm is missing the target by 5 bytes. Thus it's 5 bytes from us being able to compile all of FreeBSD with clang (and replace gcc with clang). There's #6627

Hi there! The attached patch fixes a few places where 32bit register classes or instructions are used on PowerPC64. This lets me compile a working "vim" at -O0 on PowerPC64/FreeBSD. Previously it would crash the compiler with llvm_unreachable("Impossible reg-to-reg copy"); As it was mixing 64 bit registers with 32bit ones. Vim compiled with -O2 still crashes. OK

hi! To continue the inflow of good news this week, let me announce that clang -integrated-as (ie. ELF part of MC) compiles all of FreeBSD! This includes things like booting kernel, gnu libstdc++, clang/LLVM itself and many other components that make up FreeBSD operating system. I personally consider this a milestone where -integrated-as should become the default for ELF/{x86_64,i386}. Many

On Wed, Jan 18, 2012 at 10:51:38PM +0400, Konstantin Tokarev wrote: > > > 18.01.2012, 02:46, "David Fang" <fang at csl.cornell.edu>: > > Hi, > > ?????????For anyone who might be interested, I've thrown together a little > > page to track my builds of llvm and clang, both release 3.0 and > > svn-trunk, on powerpc-darwin8. > > > >