On Fri, May 11, 2007 at 05:21:01PM -0700, Bill Wendling wrote:
> On May 11, 2007, at 5:15 PM, Mark Mitchell wrote:
> >Bill Wendling wrote:
> >>This one was just filed against 4.2.0:
> >>
> >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31903
> >>
> >>It is causing LLVM (at least) to fail to build. Do you think it's
> >>worth
> >>adding to the list?
> >
> >Does it show up anywhere other than Darwin? On the basis of Darwin
> >alone, I would not further hold up the release. That is not to say
> >that
> >I would not consider a patch to fix it, of course.
> >
> Andrew Pinski wasn't able to reproduce the link error on Linux, and
> I've only seen it on Darwin. However, as Chris Lattner pointed out,
> this indicates a fairly serious problem (which shows up even on the
> Linux build) in that the symbols aren't getting internal linkage
> (they're in an anonymous namespace, so should). It could impact
> performance on large systems quite a bit. Certainly during linking.
Shipping FSF releases already have that problem. Just try
-----------
namespace {
int foo = 0;
}
int bar = foo;
-----------
and look at the output with 4.1.2.
