From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 77585 invoked by alias); 27 Oct 2015 14:59:52 -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 77570 invoked by uid 89); 27 Oct 2015 14:59:52 -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_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mga01.intel.com Received: from mga01.intel.com (HELO mga01.intel.com) (192.55.52.88) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 27 Oct 2015 14:59:50 +0000 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga101.fm.intel.com with ESMTP; 27 Oct 2015 07:59:49 -0700 X-ExtLoop1: 1 Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by orsmga001.jf.intel.com with ESMTP; 27 Oct 2015 07:59:48 -0700 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by IRSMSX108.ger.corp.intel.com (163.33.3.3) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 27 Oct 2015 14:59:47 +0000 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.150]) by irsmsx111.ger.corp.intel.com ([169.254.2.212]) with mapi id 14.03.0248.002; Tue, 27 Oct 2015 14:59:47 +0000 From: "Tedeschi, Walfred" To: Eli Zaretskii CC: "palves@redhat.com" , "brobecker@adacore.com" , "gdb-patches@sourceware.org" Subject: RE: [PATCH v1] ABI changes for Intel(R) MPX. Date: Tue, 27 Oct 2015 17:21:00 -0000 Message-ID: References: <1445864086-4831-1-git-send-email-walfred.tedeschi@intel.com> <1445864086-4831-6-git-send-email-walfred.tedeschi@intel.com> <83ziz5bodv.fsf@gnu.org> In-Reply-To: <83ziz5bodv.fsf@gnu.org> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-10/txt/msg00626.txt.bz2 Eli, Thanks a lot for your review! I will use your version and remove also the (R). Thanks again, -Fred -----Original Message----- From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-owner@sourceware= .org] On Behalf Of Eli Zaretskii Sent: Monday, October 26, 2015 5:12 PM To: Tedeschi, Walfred Cc: palves@redhat.com; brobecker@adacore.com; gdb-patches@sourceware.org Subject: Re: [PATCH v1] ABI changes for Intel(R) MPX. > From: Walfred Tedeschi > Cc: gdb-patches@sourceware.org, Walfred Tedeschi=20 > > Date: Mon, 26 Oct 2015 13:54:46 +0100 >=20 > doc: > gdb.texinfo: (Intel(R) Memory Protection Extensions): Add > documentation on performing program function calls. Is it possible to lose the "(R)" part here? It gets in the way of Emacs sy= ntax highlighting of ChangeLog entries. > +While calling functions of an MPX enabled program boundary registers=20 > +have to be initialized before performing the call. Intended to avoid=20 > +unexpected side effects, as receiving a bound violation signal while=20 > +performing the operation. Nevertheless is possible to change the=20 > +boundary values if desired in placing a breakpoint at the end of the=20 > +prologue and setting bound registers as wished. > +After the call is performed bound register might be keept or not for=20 > +further investigations. The behaviour of initializing bounds on=20 > +returning from a program function calls can be controlled and=20 > +vizualized via the commands @table @code @kindex set=20 > +mpx-bnd-init-on-return When set to 1 bound registers will be=20 > +initialized when returning from a calling a program function @kindex=20 > +show mpx-bnd-init-on-return Show the state of mpx-bnd-init-on-return. > +@end table There are a few English and Texinfo issues here, so I suggest the following= minor rewording (please make sure I didn't change the meaning of what you = intended to say): While calling functions of an MPX enabled program, boundary registers have to be initialized before performing the call, to avoid unexpected side effects, such as a bound violation exception, while performing the operation. Nevertheless, is possible to change the boundary values, if desired, by placing a breakpoint at the end of the prologue and setting bound registers as wished in the commands of that breakpoint. After the call is performed, a bound register might or might not be keept= for further investigations. The behaviour of initializing bounds on returning from a program function calls can be controlled and displayed using the following commands: @table @code @kindex set mpx-bnd-init-on-return @item set mpx-bnd-init-on-return When set to 1, bound registers will be initialized when returning from a calling a program function. @kindex show mpx-bnd-init-on-return @item show mpx-bnd-init-on-return Show the state of @code{mpx-bnd-init-on-return}. @end table Thanks. Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul Chairperson of the Supervisory Board: Tiffany Doon Silva Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928