search for: r80071

Any chance that we could get r80071 applied to llvm-gcc-2.4 2.6 branch in about a week? As Mike said this change should be very safe. Jack On Wed, Aug 26, 2009 at 12:48:15AM -0700, Eric Christopher wrote: > > On Aug 25, 2009, at 9:57 PM, Chris Lattner wrote: > > > > > On Aug 25, 2009, at 2:33 PM,...

...> this support. Can we get this into the 2.6 release >> and trunk? > > This is fine. I don't have a rw llvm-gcc tree, some else want to > check it in? For 2.6, that's be someone else's call, for what it's > worth, this should be fairly safe. I applied this as r80071. However, I don't understand what this does. I'm able to build a working i386/x86-64 compiler on darwin without this, what exactly does this fix? What exactly is an "i386 multilib" and why do we care? :) -Chris

On Aug 26, 2009, at 2:11 PM, Jack Howarth wrote: > Any chance that we could get r80071 applied to llvm-gcc-2.4 2.6 > branch in about a week? As Mike said this change should be > very safe. Yes, I'll ask Tanya to pull it into the release. -Chris > Jack > > On Wed, Aug 26, 2009 at 12:48:15AM -0700, Eric Christopher wrote: >> >> On Aug 25, 2...

...this into the 2.6 release >>> and trunk? >> >> This is fine. I don't have a rw llvm-gcc tree, some else want to >> check it in? For 2.6, that's be someone else's call, for what it's >> worth, this should be fairly safe. > > I applied this as r80071. However, I don't understand what this > does. I'm able to build a working i386/x86-64 compiler on darwin > without this, what exactly does this fix? What exactly is an "i386 > multilib" and why do we care? :) If you build a native 64-bit darwin compiler (host/target...

...g creating clang packaging for fink as well (if the releases were coordinated and the c++ support was decent yet). Jack On Thu, Aug 27, 2009 at 05:46:39PM -0700, Chris Lattner wrote: > > On Aug 26, 2009, at 2:11 PM, Jack Howarth wrote: > >> Any chance that we could get r80071 applied to llvm-gcc-2.4 2.6 >> branch in about a week? As Mike said this change should be >> very safe. > > Yes, I'll ask Tanya to pull it into the release. > > -Chris > >> Jack >> >> On Wed, Aug 26, 2009 at 12:48:15AM -0700, Eric Christo...

On Aug 23, 2009, at 11:36 AM, Jack Howarth wrote: > Current llvm-gcc-4.2 for trunk and the 2.6 release > is unable to build the i386 multilib for the > x86_64-apple-darwin target. The attached patch provides > this support. Can we get this into the 2.6 release > and trunk? This is fine. I don't have a rw llvm-gcc tree, some else want to check it in? For 2.6, that's be

Current llvm-gcc-4.2 for trunk and the 2.6 release is unable to build the i386 multilib for the x86_64-apple-darwin target. The attached patch provides this support. Can we get this into the 2.6 release and trunk? Jack -------------- next part -------------- Index: gcc/config/i386/t-darwin64 =================================================================== ---