From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Wed, 26 Apr 2000 14:50:36 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: gcc 3.0
Message-ID: <3907023C.30855.3E86E3@localhost>
In-reply-to: <200004261520.LAA10494@envy.delorie.com>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> 
> The gcc group has announced that they're ramping up for the final gcc
> 3.0 release work.  Now is the best time for the DJGPP people working
> on/with gcc to get involved in testing the DJGPP port of gcc, and
> making sure we get our patches in.  (but don't be annoying ;)

I'd like suggestions on what to do about enabling ".weak" and ".gnu.linkonce" 
in gcc for C++ templates.

There are two options. I can go with the method used by the DJGPP port which 
uses the "-mbnu210" switch that enables the support. Or should it done 
unconditionally so that either binutils 2.9.5.1 beta or the now promised 
binutils 2.10 release are required. Since gcc 3.0 will be using a new C++ 
ABI, perhaps now is a golden opportunity to make the change and do it at the 
same time as other major C++ changes.

Mark