This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: import newer Libtool?

From: Paolo Bonzini <bonzini at gnu dot org>
To: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, gcc-patches at gcc dot gnu dot org
Date: Mon, 10 Jan 2011 09:12:48 +0100
Subject: Re: import newer Libtool?
References: <20110110070111.GC24102@gmx.de>

On 01/10/2011 08:01 AM, Ralf Wildenhues wrote:

Basically I'm asking for advice/opinions what to do with this.
Apply to a temporary branch and suggest people to test it?  Apply
to trunk, put on my flame suit and hope hell doesn't break loose?
Wait until after branching and backport from trunk to branch after
some testing period?

That's too far away.

To put things into perspective: this does fix a number of bugs
reported over the last weeks and months, but AFAIK no P1 or P2
regressions.  It should allow to build GCC with LTO (but for
parallel linking to work Automake changes would still be needed).

I'll leave it to the RM. Certainly it sounds like good changes, but can you make a list of PRs that are fixed?

Paolo

Follow-Ups:
- Re: import newer Libtool?
  - From: Richard Guenther

References:
- import newer Libtool?
  - From: Ralf Wildenhues

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]