From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12989 invoked by alias); 25 May 2016 18:24:01 -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 12972 invoked by uid 89); 25 May 2016 18:24:00 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=H*M:1a7e, love 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; Wed, 25 May 2016 18:23:59 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (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 9509685540; Wed, 25 May 2016 18:23:58 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u4PINvS4018037; Wed, 25 May 2016 14:23:57 -0400 Subject: Re: [PATCH v2][PR gdb/19893] Fix handling of synthetic C++ references To: Martin Galvan References: <1464019228-11131-1-git-send-email-martin.galvan@tallertechnologies.com> <04d07644-c6ed-88ae-f1de-cba46e875f2d@redhat.com> Cc: gdb-patches From: Pedro Alves Message-ID: <2dc66791-b716-48a1-1a7e-3e853fd38127@redhat.com> Date: Wed, 25 May 2016 18:24:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-05/txt/msg00452.txt.bz2 On 05/24/2016 09:35 PM, Martin Galvan wrote: > So I think before proceeding we should decide which output is better. > Perhaps we could show @address whenever possible, and pointer> for the corner cases? Yes, I think so. Synthetic pointers are really an implementation detail, not really something users care about. > On a related note, it'd be great (for debugging at least!) if unions > such as this had at least a discriminant of sorts. It's the value's lval type. :-) > Right now I don't think so. The existing methods should be enough to > handle these cases. Speaking of which, are there any plans to rewrite > this sort of object-oriented code in C++? I'd love to take a shot at > this in the future. Certainly, that'd be welcome. Thanks, Pedro Alves