From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29542 invoked by alias); 21 Nov 2013 16:13:14 -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 29531 invoked by uid 89); 21 Nov 2013 16:13:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_SOFTFAIL,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: mtaout20.012.net.il Received: from Unknown (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Nov 2013 16:13:11 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MWM00900FNN6Y00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Thu, 21 Nov 2013 18:13:02 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MWM0094YFPQ4I30@a-mtaout20.012.net.il>; Thu, 21 Nov 2013 18:13:02 +0200 (IST) Date: Thu, 21 Nov 2013 16:13:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 2/3] set/show code-cache In-reply-to: <528DFA57.7000601@codesourcery.com> To: Yao Qi Cc: palves@redhat.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83li0hense.fsf@gnu.org> References: <1384996594-20865-1-git-send-email-yao@codesourcery.com> <1384996594-20865-3-git-send-email-yao@codesourcery.com> <528D781A.7070909@codesourcery.com> <528DF2C5.6050705@redhat.com> <528DFA57.7000601@codesourcery.com> X-IsSubscribed: yes X-SW-Source: 2013-11/txt/msg00643.txt.bz2 > Date: Thu, 21 Nov 2013 20:19:35 +0800 > From: Yao Qi > CC: > > On 11/21/2013 07:47 PM, Pedro Alves wrote: > > Putting a user hat on, I'd be left wondering what "affecting > > correctness" means here. > > I don't have any troubles understanding "without affecting correctness". > It means GDB still behaves correctly when code-cache option is on. Right, but will the description lose something if you just omit that part? I mean, if we never say anything about correctness, users will have no reason to suspect that correctness might suffer in this case.