Date: Thu, 6 Nov 2003 18:18:24 +0100 From: Marius Strobl <marius@alchemy.franken.de> To: Alexander Kabaev <ak03@gte.com> Cc: freebsd-current@freebsd.org Subject: Re: g++ problem Message-ID: <20031106181824.B55161@newtrinity.zeist.de> In-Reply-To: <20031106115112.50b53136.ak03@gte.com>; from ak03@gte.com on Thu, Nov 06, 2003 at 11:51:12AM -0500 References: <200311061555.hA6Ft08H051563@www.kukulies.org> <20031106112828.7985100a.ak03@gte.com> <20031106174459.A55161@newtrinity.zeist.de> <20031106115112.50b53136.ak03@gte.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 06, 2003 at 11:51:12AM -0500, Alexander Kabaev wrote: > On Thu, 6 Nov 2003 17:44:59 +0100 > Marius Strobl <marius@alchemy.franken.de> wrote: > > > This happens with g++ 3.x ... > This will happen with g++ 3.x, 2.x, 1.x and future 4.x too. I.e. the > GCC is not at fault and the subject of the original message is > misleading. > It's at least not fatal with g++ 2.95.4 on 4-stable, that's what I meant. But yes, GCC is not at fault.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031106181824.B55161>