This is the mail archive of the
mailing list for the GCC project.
Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin
- From: Jack Howarth <howarth at bromo dot msbb dot uc dot edu>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 29 Feb 2008 20:58:44 -0500
- Subject: Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin
- References: <20080229141451.GA22429@bromo.msbb.uc.edu> <email@example.com> <20080229173552.GA5296@bromo.msbb.uc.edu> <47C85738.firstname.lastname@example.org> <20080229195213.GA3059@bromo.msbb.uc.edu> <47C863AD.email@example.com>
One other question. Does the bug fixed by the offending patch...
...merit breaking even a secondary target? Wouldn't it be better
to regress that patch out for gcc 4.3.0 (to be reintroduced in
gcc 4.3.1 when the problems that it causes for darwin are solved)?
On Fri, Feb 29, 2008 at 11:57:33AM -0800, Mark Mitchell wrote:
> Jack Howarth wrote:
>> I can understand the FSF gcc developers' frustration at
>> the lack of participation by the darwin developers. However
>> I still think it merits at least understanding why r131198
>> is breaking the linkage on darwin. It may well be that darwin
>> to exposing a latent bug in the use of install-leaf.
> I didn't mean to imply otherwise. My statement was simply that Darwin-only
> problems are not in and of themselves release-blockers for 4.3.0.
> Mark Mitchell
> (650) 331-3385 x713