From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12370 invoked by alias); 24 Nov 2007 02:00:51 -0000 Received: (qmail 12338 invoked by uid 22791); 24 Nov 2007 02:00:47 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 24 Nov 2007 02:00:43 +0000 Received: (qmail 26087 invoked from network); 24 Nov 2007 02:00:41 -0000 Received: from unknown (HELO ?192.168.0.2?) (mitchell@127.0.0.2) by mail.codesourcery.com with ESMTPA; 24 Nov 2007 02:00:41 -0000 Message-ID: <474785BC.1060305@codesourcery.com> Date: Sat, 24 Nov 2007 10:42:00 -0000 From: Mark Mitchell User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Ian Lance Taylor CC: gcc-patches@gcc.gnu.org, amodra@bigpond.net.au Subject: Re: PATCH RFC: Add -fmerge-debug-strings option References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2007-11/txt/msg01272.txt.bz2 Ian Lance Taylor wrote: > 2007-11-16 Ian Lance Taylor > > * common.opt (fmerge-debug-strings): New option. > * dwarf2out.c (DEBUG_STR_SECTION_FLAGS): Test > flag_merge_debug_strings rather than flag_merge_constants. > * doc/invoke.texi (Option Summary): Mention > -fmerge-debug-strings. > (Debugging Options): Document -fmerge-debug-strings. I agree with you and I think this patch should be checked in. > +@item -fmerge-debug-strings > +@opindex fmerge-debug-strings > +Direct the linker to merge together strings which are identical in > +different object files. This is not supported by all assemblers or > +linker. This decreases the size of the debug information in the "linkers" > +output file at the cost of increasing link processing time. This is > +on by default. Do we have a convention about whether we document -ffoo or -fno-foo in the manual? (I could imagine documenting -fno-foo for options on by default, since -fno-foo is probably what users would want to know how to use.) Thanks, -- Mark Mitchell CodeSourcery mark@codesourcery.com (650) 331-3385 x713