Release Branch for llvm-gcc

Dear All,

I would like to create the release branch for the llvm-gcc source code tomorrow morning. I imagine this will be okay as llvm-gcc seems pretty healthy and no one is currently doing any development on it.

If there's something that needs to be fixed, or you're working on llvm-gcc, please email the list so that I can delay creating the branch as appropriate.

I won't be creating the LLVM release branch until the current work on LLVM is finished, which I believe is planned to be about a week or two from now.

Thanks.

-- John T.

Sounds great!

-Chris

I would like to create the release branch for the llvm-gcc source code tomorrow morning. I imagine this will be okay as llvm-gcc seems pretty healthy and no one is currently doing any development on it.

If there's something that needs to be fixed, or you're working on llvm-gcc, please email the list so that I can delay creating the branch as appropriate.

I won't be creating the LLVM release branch until the current work on LLVM is finished, which I believe is planned to be about a week or two from now.

I thought I should warn you the Cygwin Release (ENABLE_OPTIMIZED=1) build fails due to 'ld/collect2' assertion failure.

This is really a Cygwin problem that I thought would be fixed with time by now but is still present with GCC 3.4.4 and binutils 2.16.91.

If there is no one else looking into fixing this then I will take a crack at updating Cygwin to later GCC and binutils versions.

Aaron

Aaron

Aaron

Is there a version of Cygwin that _does_ build LLVM in release mode?
If not, we might as well put a prominent warning for people to not be
surprised.

Is there a version of Cygwin that _does_ build LLVM in release mode?

No. There are no versions of Cygwin anyway, only the most rescent. You may choose versions of particular packages but even this is limited to the last 2 or 3 versions. On Cygwin if things get broken in new releases and the old ones are dropped then if is tough so to speak :frowning:

gcc 2.95.3 may have been fine, but cannot be built by Cygwin anymore.

Even binutils was/is(?) broken under Cygwin, only the documentation though so there is a work around.

Cygwin is like a poor cousin to GNU/Linux.

If not, we might as well put a prominent warning for people to not be
surprised.

Yep. The LLVM online instructions only give the debug build anyway, so unless you try the release/optimized build for your self then you do not bump into the problem.

The only thing is the debug build is ten times slower at linking than the release build would be.

Anyway when I get some time I will try updating to GCC 4 and see if that solves the problem. If not then I will see if I can narrow the problem down and do a bug report to GCC or binutils.

The problem is with COFF (Common Object File Format) encoding and decoding between GCC and binutils. Binutils is throwing an assertion failure for a number of object modules, LLVMPowerPC.o, LLVMX86.o and LLVMDebugger.o.

Aaron