From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-132111-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 48257 invoked by alias); 14 Jun 2016 17:03:46 -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 48242 invoked by uid 89); 14 Jun 2016 17:03:45 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:335, Involve
X-HELO: mx1.redhat.com
Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 14 Jun 2016 17:03:44 +0000
Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24])	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))	(No client certificate requested)	by mx1.redhat.com (Postfix) with ESMTPS id 87BA23B709;	Tue, 14 Jun 2016 17:03:43 +0000 (UTC)
Received: from host1.jankratochvil.net (ovpn-116-44.ams2.redhat.com [10.36.116.44])	by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u5EH3eVU006967	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);	Tue, 14 Jun 2016 13:03:42 -0400
Date: Tue, 14 Jun 2016 17:03:00 -0000
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, Pedro Alves <palves@redhat.com>,        gdb-patches@sourceware.org
Subject: Re: [PING][PATCH 2/2] Involve gdbarch in taking DWARF register pieces
Message-ID: <20160614170339.GA27342@host1.jankratochvil.net>
References: <20160415180943.4FEE857EE@oc7340732750.ibm.com> <571134CD.8080507@redhat.com> <m3shyjw2t3.fsf@oc1027705133.ibm.com> <5714E6EA.8050905@redhat.com> <m3lh4bvu2z.fsf@oc1027705133.ibm.com> <57150356.3090508@redhat.com> <m3a8kpx0ls.fsf@oc1027705133.ibm.com> <m3h9elvpc7.fsf_-_@oc1027705133.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m3h9elvpc7.fsf_-_@oc1027705133.ibm.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
X-IsSubscribed: yes
X-SW-Source: 2016-06/txt/msg00255.txt.bz2

On Thu, 28 Apr 2016 15:24:08 +0200, Andreas Arnez wrote:
> IIRC, there was some uncertainty about the clarity/meaning of the new
> gdbarch method's description below.  Or has this cleared up by now?

Ping (to Andreas Arnez) as this thread remained unfinished.


Jan