From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26595 invoked by alias); 6 Jan 2015 03:31:54 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 26550 invoked by uid 89); 6 Jan 2015 03:31:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout26.012.net.il Received: from mtaout26.012.net.il (HELO mtaout26.012.net.il) (80.179.55.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 06 Jan 2015 03:31:41 +0000 Received: from conversion-daemon.mtaout26.012.net.il by mtaout26.012.net.il (HyperSendmail v2007.08) id <0NHQ00G00K6D8F00@mtaout26.012.net.il> for gdb-patches@sourceware.org; Tue, 06 Jan 2015 05:31:13 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout26.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NHQ000XSKG1KH70@mtaout26.012.net.il>; Tue, 06 Jan 2015 05:31:13 +0200 (IST) Date: Tue, 06 Jan 2015 03:31:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH] "info source" now includes producer string In-reply-to: To: Doug Evans Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <8361ck8tzx.fsf@gnu.org> References: <838uhh7y0t.fsf@gnu.org> X-IsSubscribed: yes X-SW-Source: 2015-01/txt/msg00065.txt.bz2 > Date: Mon, 5 Jan 2015 16:28:20 -0800 > From: Doug Evans > Cc: gdb-patches > > >> +* The "info source" command now displays the producer string if it was > >> + present in the debug info. > > > > I wonder whether we should replace "producer" with something less > > abstract. Would "compilation command line" be accurate enough? > > The producer string can be anything, it's whatever the compiler > decides, so I'm really hesitant to be specific here (and "command > line" is too specific for me), because often it will be wrong. We can always say "e.g." or "such as". That would at least describe the most frequent use cases. We don't have to be 110% accurate here, just clear enough to convey the intent.