From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66602 invoked by alias); 25 Aug 2016 23:28: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 66588 invoked by uid 89); 25 Aug 2016 23:28:00 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=langhook X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 25 Aug 2016 23:27:50 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=SVR-IES-FEM-01.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1bd43p-0007Yt-41 from joseph_myers@mentor.com ; Thu, 25 Aug 2016 16:27:49 -0700 Received: from digraph.polyomino.org.uk (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.3.224.2; Fri, 26 Aug 2016 00:27:47 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.86_2) (envelope-from ) id 1bd43l-0006Y7-Vu; Thu, 25 Aug 2016 23:27:46 +0000 Date: Thu, 25 Aug 2016 23:28:00 -0000 From: Joseph Myers To: Ulrich Weigand CC: Subject: Re: [9/9] Support __float128 format on Intel and Power In-Reply-To: <20160825150829.9A434C9FB@oc7340732750.ibm.com> Message-ID: References: <20160825150829.9A434C9FB@oc7340732750.ibm.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2016-08/txt/msg00277.txt.bz2 On Thu, 25 Aug 2016, Ulrich Weigand wrote: > Since at this point we do not yet have any indication in the debug info to > distinguish different floating-point formats of the same length, we simply > use the type name as hint. Types named "__float128" get the IEEE format. Note that now (GCC 7) __float128 is a built-in typedef (i.e. a name registered with the register_builtin_type langhook) for _Float128, and _Float128 is the primary name used when the type is created. If I build a program with GCC 7 that uses __float128, the debug info I get references _Float128 (and not __float128 as far as I can see). Obviously debugging should work whether someone uses _Float128 or __float128 (and in C++, right now they can only use __float128, as the keyword _Float128 is C-specific). Then on Power, _Float64x is also binary128 when available (but is a distinct type at the C level from _Float128), but on x86 it has the Intel extended format (but is a distinct type from long double). -- Joseph S. Myers joseph@codesourcery.com