From owner-freebsd-current Fri Apr 30 12:15:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 2B63714BFA for ; Fri, 30 Apr 1999 12:15:18 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA59569; Fri, 30 Apr 1999 20:15:56 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 30 Apr 1999 20:15:56 +0100 (BST) From: Doug Rabson To: obrien@NUXI.com Cc: John Polstra , sprice@hiwaay.net, current@freebsd.org Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... In-Reply-To: <19990430114829.B95710@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, David O'Brien wrote: > > These are good questions, and I don't know enough yet about the issues > > surrounding vtable thunks to answer them. > > I haven't had time to really dig into this yet. Hopefully Saturday. I'm > about to revert the change until I can see what the problem is and what > the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug > time frame. Of course I will try to upgrade us to it (well 1.2.1 which I > figure will quickly follow). The EGCS maintainers are pushing to get > vtable thunks working properly for 1.2. > > Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has > posted a bug report related to them, there is an option to turn them off, > and this *is* -CURRENT. I may just leave them turned on by default. > > Opinions? I would prefer to keep vtable thunks turned on. The alternative produces wretched code for multiple inheritance. Personally, I want -fnew-abi too; gcc does some disgusting things with multiple zero-sized base classes without it... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message