From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-107490-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 15882 invoked by alias); 21 Nov 2013 20:48:14 -0000
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
Received: (qmail 15850 invoked by uid 89); 21 Nov 2013 20:48:13 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_PASS autolearn=no version=3.3.2
X-HELO: mail-vb0-f54.google.com
Received: from Unknown (HELO mail-vb0-f54.google.com) (209.85.212.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Thu, 21 Nov 2013 20:48:12 +0000
Received: by mail-vb0-f54.google.com with SMTP id p6so222379vbe.13        for <gdb-patches@sourceware.org>; Thu, 21 Nov 2013 12:48:04 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:date         :message-id:subject:from:to:cc:content-type;        bh=5elpkBLCU6n3Yv4RMAbXD92LLHHdsyn2QmavaZ25YQU=;        b=cfS3uVUqA5MjdoyeGnPva4nfHrSjif/md1J8T7b7wOAx2v+yiCLgdnqB5/QbnL4ly1         w2N0tcb0jmRvD7nW9J/gIamqOlMdEg4g6DK1rwRqgZZrc3LYZfUSk/JOPB83UJr2ByGH         flR16J+RiY3qK9uffYubU0EWQ/fFL1tu4suZtNdXAqGRGOXgiJs87RK2vGh7vycI1Nlz         fNSnEmO39kMRrcPFgaAEPDx8X+HsylVHncpr4ktStRZFwv3+/vyZnRG2FTThqHNlD9zw         pMXIj8e+kTi+MK3MzcW/Vti0luODH/Hw/xrMBehCFXrqf/HQyDU6xel/JllTzNdy23pE         vKig==
X-Gm-Message-State: ALoCoQmCuu5ws2zNjAmQbU2uPiiGTwyTodNi9ZNYvkoL3Y9y81EsnS+sGo8BJC9v9FpAdwundJL/6aPNlkenTlwioCOeLtVKgjrAlTEcgnR7BHQECzlJ/jIMDXZHGup3MEfbhU+tsn4P7FV5BVYsDoSqk7mHbmAtqvES7zi6cl/kAkc9aOLBioaQSnJUpJkVQG3lLfISgjUywn2HKzciVYXhi5j8btItbQ==
MIME-Version: 1.0
X-Received: by 10.220.58.1 with SMTP id e1mr7625405vch.0.1385066884530; Thu, 21 Nov 2013 12:48:04 -0800 (PST)
Received: by 10.52.163.52 with HTTP; Thu, 21 Nov 2013 12:48:04 -0800 (PST)
In-Reply-To: <528DF2C5.6050705@redhat.com>
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>
Date: Thu, 21 Nov 2013 20:50:00 -0000
Message-ID: <CADPb22S4xhzVOAsupB-yVK=ixzgpy9wF2M2to=ZwF33YtoT6fA@mail.gmail.com>
Subject: Re: [PATCH 2/3] set/show code-cache
From: Doug Evans <dje@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches <gdb-patches@sourceware.org>
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
X-SW-Source: 2013-11/txt/msg00657.txt.bz2

On Thu, Nov 21, 2013 at 3:47 AM, Pedro Alves <palves@redhat.com> wrote:
> On 11/21/2013 03:03 AM, Yao Qi wrote:
>> +@kindex set code-cache
>> +@item set code-cache on
>> +@itemx set code-cache off
>> +Enable or disable caching of code segment accesses.  When @code{ON},
>> +use caching.  By default, this option is @code{ON}.  This improves
>> +performance of disassembly in remote debugging without affecting
>> +correctness.
>> +
>
> Putting a user hat on, I'd be left wondering what "affecting
> correctness" means here.

I wondered about this and left it as is, given that's what's written
for the stack-cache case.