This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A glibc or egcs bug?
- To: drepper at ipd dot info dot uni-karlsruhe dot de
- Subject: Re: A glibc or egcs bug?
- From: hjl at lucon dot org (H.J. Lu)
- Date: Sat, 6 Dec 1997 23:46:56 -0800 (PST)
- Cc: egcs at cygnus dot com, libc-linux at gnu dot org
>
> hjl@lucon.org (H.J. Lu) writes:
>
> > This is from glibc 2.1:
> >
> > # gcc -v
> > Reading specs from
> > /usr/lib/gcc-lib/i586-unknown-linux-gnulibc1/egcs-2.90.20/specs
> > gcc version egcs-2.90.20 971201 (gcc2-970802 experimental)
> > # gcc -S w.cc
> > w.cc: In function `int foo()':
> > w.cc:48: no matching function for call to `__WAIT_STATUS::._2 (int *)'
> > w.cc:38: candidates are: __WAIT_STATUS::._2(const {anonymous union} &)
> > w.cc:38: __WAIT_STATUS::._2()
>
> I've changed glibc earlier this week to not use transparent unions for C++.
> This is unfortunate since the avoiding casts is always good but maybe it's
> too difficult to change the C++ lookup handling. Jason?
>
But glibc 2.1 971205 still has the old code.
--
H.J. Lu (hjl@gnu.org)