Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin

2008-03-02 Thread Mark Mitchell
Jack Howarth wrote: Do we have any other targets that link gcc (and xgcc) with the shared libgcc? I see that i386 and x86_64 linux creates a gcc (and xgcc) linked to the static libgcc. If any other targets use a shared libgcc for gcc (and xgcc) they may be broken as well. That's a good hint

Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin

2008-03-01 Thread Jack Howarth
Mark, While I don't see any particular differences in how gcc 4.3 branch links its shared libraries with or without r131198 applied, I do notice that it causes the xgcc created to be linked against the system libgcc. Without r131198, only the xgcc in stage1-gcc is linked to the system libgcc. Wi

Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin

2008-02-29 Thread Mark Mitchell
Jack Howarth wrote: Mark, One other question. Does the bug fixed by the offending patch... http://gcc.gnu.org/ml/gcc-patches/2007-12/msg01010.html ...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 th

Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin

2008-02-29 Thread Jack Howarth
Mark, One other question. Does the bug fixed by the offending patch... http://gcc.gnu.org/ml/gcc-patches/2007-12/msg01010.html ...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 cau

Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin

2008-02-29 Thread Mark Mitchell
Jack Howarth wrote: Mark, 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

Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin

2008-02-29 Thread Jack Howarth
Mark, 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.

Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin

2008-02-29 Thread Mark Mitchell
Jack Howarth wrote: Richard, This problem appears to be caused by... Author: rsandifo Date: Thu Dec 27 11:26:06 2007 New Revision: 131198 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131198 Log: libgcc/ * Makefile.in (all): Use install-leaf rather than install. (ins

Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin

2008-02-29 Thread Jack Howarth
Richard, This problem appears to be caused by... Author: rsandifo Date: Thu Dec 27 11:26:06 2007 New Revision: 131198 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131198 Log: libgcc/ * Makefile.in (all): Use install-leaf rather than install. (install): Split most of t

Re: PR35401 and PR30572 are gcc 4.3.0 release blockers on darwin

2008-02-29 Thread Richard Guenther
On Fri, Feb 29, 2008 at 3:14 PM, Jack Howarth <[EMAIL PROTECTED]> wrote: >Current gcc 4.3 branch incorrectly links all of its > shared libraries against the system libgcc instead of > the copy it builds and installs (PR35401). It appears > that the fix applied for PR30572 may have been > di