From mboxrd@z Thu Jan  1 00:00:00 1970
From: hjl@lucon.org (H.J. Lu)
To: drepper@ipd.info.uni-karlsruhe.de
Cc: egcs@cygnus.com, libc-linux@gnu.org
Subject: Re: A glibc or egcs bug?
Date: Sat, 06 Dec 1997 23:47:00 -0000
Message-id: <m0xebQW-0004ecC@ocean.lucon.org>
References: <x7oh2tdbsa.fsf@myware.rz.uni-karlsruhe.de>
X-SW-Source: 1997-12/msg00393.html

> 
> 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)