similar to: [LLVMdev] Build problem with gcc-4.3.2

I've been getting the error for a release build for the last 24 hours or so. This is on Ubuntu Jaunty on x86. Known problem? If not, does anyone have an easy recipe for getting the build system to tell me the command line that's being used and to leave a preprocessed file sitting around? Thanks, John llvm[2]: Compiling UnreachableBlockElim.cpp for Release build

There have been a couple problems recently, but I don't recognize this. Please see if you can minimize it and get a test case. You can run with 'make VERBOSE=1' to get the failing compile command. I then usually try -emit-llvm to see if the .bc output reproduces the error (with llc). The full story is a lot more complicated, I can give more details about things to try if you can't

Hi, I have a question regarding StrongPHIElimination. With (weak) PHIElimination, register classes seems to take care of themselves, but with the Strong version, I get illegal virtual register for instruction. In this testcase, I define the PHI operands into a bigger (super) RC, than what the using MI can handle. Weak PHI elim handled this by copying the PHI operands into the right RC. The

Hello, I am implementing a code transformation that would heavily benefit from the CodeGen/StrongPHIElimination pass, but on the two bytecode files I've tested it on so far llc segfaults on both. I see there have been no substantive changes to this code since the middle of last year. Could someone please tell me what the status of this pass is? Thank you. Marc -------------- next part

On Feb 8, 2013, at 4:20 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: > On Feb 8, 2013, at 4:03 PM, Cameron Zwarich <zwarich at apple.com> wrote: > >> How much of the work is done here? I'd be happy to do the phi elimination part, since I basically did that for StrongPhiElimination (RIP). > > Any help would be appreciated. > > I did a bit of the

There was a patch that went thru for this recently from Rafael Espindola. The fix is on the mirror. Index: gcc/dwarf2out.c =================================================================== --- gcc/dwarf2out.c (revision 120589) +++ gcc/dwarf2out.c (working copy) @@ -14361,9 +14361,8 @@ s->refcount++; /* Avoid unnecessarily putting strings that are used less than twice in the hash

On Feb 8, 2013, at 4:03 PM, Cameron Zwarich <zwarich at apple.com> wrote: > How much of the work is done here? I'd be happy to do the phi elimination part, since I basically did that for StrongPhiElimination (RIP). Any help would be appreciated. I did a bit of the easy stuff in 2-addr, it has a LIS = getAnalysisIfAvailable<LiveIntervals>() member that it sometimes updates. It

Is there a way to make samba automatically mount a home directory? That is, a user logging in (from Linux), enters its username and password(Samba), and the system automatically mounts the user's home directory from the samba server(without asking the password again). Has anyone ever tried to do this? And succedeed :-) ? -- nneves@di.fc.ul.pt Dept. Informatica, Fac.

And how about this one for handling the C specific invoke_impl_ptr_type? Index: gcc-4.2.llvm/gcc/c-common.h =================================================================== --- gcc-4.2.llvm.orig/gcc/c-common.h 2008-07-30 21:01:49.000000000 +0200 +++ gcc-4.2.llvm/gcc/c-common.h 2008-07-30 21:01:56.000000000 +0200 @@ -1164,7 +1164,6 @@ extern struct block_sema_info *cur_block; extern tree

I'm the person who wrote it, and it's not really maintained, as we decided we wanted to go in a different direction long-term by having fewer passes making independent coalescing decisions rather than more. At the time I stopped working on it, it worked fine on x86 but caused problems with armv7 NEON code. If you file a PR with a test case, I am happy to take a quick look and try to fix

I will try to make a standalone test case but the one that is failing uses a custom back end, so it's not really portable. So is the plan to have the strong PHI elimination behavior rolled into other passes? Andrew On 06/20/2012 06:54 PM, Cameron Zwarich wrote: > I'm the person who wrote it, and it's not really maintained, as we decided we wanted to go in a different direction

On Wednesday 30 July 2008 18:13:27 Duncan Sands wrote: > On x86-64 linux, in stage 2, I get: > > c++ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -o f951 \ > fortran/arith.o

On Jul 30, 2008, at 11:39 AM, Duncan Sands wrote: > On Wednesday 30 July 2008 18:13:27 Duncan Sands wrote: >> On x86-64 linux, in stage 2, I get: >> >> c++ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict- >> prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno- >> variadic-macros -Wno-overlength-strings -Wold-style-definition - >>

I'm getting a build error when trying to build gcc4 from sources. This is for the recent 1.9 release. How I built llvm-1.9: ----------------------------- tar zxf llvm-1.9.tar.gz cd llvm-1.9/ ./configure --prefix=/custom/llvm-1.9 make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION='-O2' tools-only make install How I built gcc4: ----------------------------- export

On x86-64 linux, in stage 2, I get: c++ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -o f951 \ fortran/arith.o fortran/array.o fortran/bbt.o fortran/check.o fortran/data.o fortran/decl.o

Hello, I've encountered a problem similar to 'lost-copy' when using the StrongPhiElimination and wonder whether it is a incompatibility issue between the two different algorithms used in StrongPhiElimination.cpp. The StrongPhiElimination is mostly based on the algorithm in Zoran Budimilic et al's "Fast Copy Coalescing and Live-Range Identification" ([1]), while the

How much of the work is done here? I'd be happy to do the phi elimination part, since I basically did that for StrongPhiElimination (RIP). IIRC you run into a lot of problems with NEON subregister defs, which might be fixed by your new direct LiveIntervals implementation. Cameron On Feb 8, 2013, at 3:41 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: > I just enabled a new

Attached is a port of the new ARM eabi from gcc 4.1 to the llvm-gcc branch. With this patch I am able to bootstrap the 4.0 branch using the new eabi. The llvm-gcc branch fails with ------------------------------------ internal compiler error: in prune_unused_types_update_strings, at dwarf2out.c:14372 ------------------------------------ But I believe that this is an unrelated problem and I will

Hi RamShankar, On top of Rafael mentioned ,Please check with lib/CodeGen/StrongPHIElimination.cpp and the papers like Budimlic, et al. Fast copy coalescing and live-range identification. // In Proceedings of the ACM SIGPLAN 2002 Conference on Programming Language // Design and Implementation (Berlin, Germany, June 17 - 19, 2002). // PLDI '02. ACM, New York, NY, 25-32. Boissinot,

On Apr 13, 2008, at 1:28 PM, Török Edwin wrote: > Hi, > > In PR2193 LiveVariables runs out of memory on a 512M limit, after > processing 11557 basicblocks. > VirtRegInfo has ~180000 entries with ~700 bytes each. > If I give it more memory (1.5G) it runs out of memory in LiveInterval. Some of the information kept by LiveVariables are somewhat redundant and can be removed. I