This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: powerpc-linux: C++ looks completly broken
- To: Daniel Berlin <dberlin at redhat dot com>
- Subject: Re: powerpc-linux: C++ looks completly broken
- From: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>
- Date: Wed, 21 Feb 2001 16:56:03 +0100
- Cc: Andreas Jaeger <aj at suse dot de>,gcc at gcc dot gnu dot org
- References: <hohf1o14fu.fsf@gee.suse.de><hohf1o14fu.fsf@gee.suse.de>
At 16:20 21.02.2001, Daniel Berlin wrote:
>Andreas Jaeger <aj@suse.de> writes:
>
> > Trying to run today's gcc-3.0 branch from CVS on powerpc with glibc
> > 2.2, binutils 2.10.91.0.2 (from HJ - similiar to binutils from CVS) I
> > get a huge number of failures for C++. I'm sending the test log
> > separatly to gcc-testresults@gcc.gnu.org. Looking at the archives I
> > noticed that Franz has only a few failures - but everybody else
> > reporting powerpc-linux bootstrap has these over 900 failures.
> >
> > Franz, why are your results better than those from the other folks?
> > Are you using extra patches? Can you make them available and get them
> > integrated into GCC, please?
> >
> > Looking through g++.log I notice that most failures are like the
> > following:
> >
> > FAIL: g++.benjamin/tem06.C (test for excess errors)
> > /usr/src/packages/BUILD/gcc/obj/gcc/testsuite/../libgcc_s.so: undefined
> reference to `__SBSS2_END__'
> > /usr/src/packages/BUILD/gcc/obj/gcc/testsuite/../libgcc_s.so: undefined
> reference to `__init'
> > /usr/src/packages/BUILD/gcc/obj/gcc/testsuite/../libgcc_s.so: undefined
> reference to `__SBSS_END__'
> > /usr/src/packages/BUILD/gcc/obj/gcc/testsuite/../libgcc_s.so: undefined
> reference to `__SDATA2_START__'
> > /usr/src/packages/BUILD/gcc/obj/gcc/testsuite/../libgcc_s.so: undefined
> reference to `__SDATA_START__'
> > collect2: ld returned 1 exit status
> >
> > What's going on with __SBSS2_END__ ? It seems that at the moment C++
> > support for PowerPC is broken.
>
>I get this too.
>I didn't a week ago.
>In fact, I know it wasn't like this at the beginning of february,
>because the new-register allocator branch was from the beginning of
>feb, and it didn't have this problem.
>
>I'll tell if it's libstdc++-v3 or g++ in a moment, the new-regalloc-branch
>has an up-to-date gcc subdir, but i never merged libstdc++-v3 to HEAD,
>so it's still from the beginning of feb.
The reason is rather clear, it's the change to shared libgcc that broke it,
and for pure powerpc-linux a simple workaround exists as you can see from
my other post.
You should rather spend your time tracking down why the 2.4 kernel fails to
compile with -gdwarf-2 -feliminate-dwarf2-dups, it stops somewhere in
drivers/ide :-).
Franz.