From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) by sourceware.org (Postfix) with ESMTPS id D24423836C5D for ; Thu, 11 Mar 2021 15:14:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D24423836C5D Received: by mail-wm1-x331.google.com with SMTP id r15-20020a05600c35cfb029010e639ca09eso13425545wmq.1 for ; Thu, 11 Mar 2021 07:14:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2gsjR9BM1/Om/A6Nfxu8zodqmZsBD1YyZGCwtNMcyUc=; b=NqGnsC2fEcmkgoWqTd22tY56P4V63WhkO6TboZdlXtLG2h8SnJRdCrGEcVKBzPq4eW gLZcu+DvHtzFUvSnmQrIZUlXS/nDv1/bD2n2ljNuwQZ3wv/Tur2562/XnPqIKgvVNPtF NZm5BUobV7I6bydc0VMNa9Q2UzJw4z4lBzCTsgNAww2eTOOREyjtupASn773pm8rZm8x a/SP3OYDJDbvM23fMNENc7Ln3TIVFgDeFxsvUcSPhabaCLPK/H+M8jQ0EmEdy42B/IbN FaHbC2Eja5BBHt/kUicgXlldq/8aIJDX9bigDJXphEgONPPp2YGEj3xq4IMlErvPzsBO wqSg== X-Gm-Message-State: AOAM531OjBTMpSLYV8c34PBqpNhWQOXSpIER7FKnGYl2ic6g/ec1IpUr g3zcWk8UtpiXTRzenKDIyZz0uYQ/Fa9nWsvpRLE= X-Google-Smtp-Source: ABdhPJy6lhTqADckizzRJK/AiG/h0fxPeTiaCbGFQvnZVTnnHP2RaXcD9f7reMVJmV7X7Mug3xcjNlwqqE7nH3Qn5BI= X-Received: by 2002:a7b:c7ca:: with SMTP id z10mr8627227wmk.117.1615475652925; Thu, 11 Mar 2021 07:14:12 -0800 (PST) MIME-Version: 1.0 References: <8bf4aad6-390d-3735-5c8c-457f036c379f@gmail.com> In-Reply-To: <8bf4aad6-390d-3735-5c8c-457f036c379f@gmail.com> From: Jonathan Wakely Date: Thu, 11 Mar 2021 15:14:01 +0000 Message-ID: Subject: Re: IEEE Interchange floating point and extended floating point for C++ To: Gabriel Ravier Cc: "gcc@gcc.gnu.org" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2021 15:14:20 -0000 On Thu, 11 Mar 2021 at 15:07, Gabriel Ravier via Gcc wrote: > > On 3/11/21 1:56 PM, Jonathan Wakely via Gcc wrote: > > On Thu, 11 Mar 2021 at 09:43, Kito Cheng via Gcc wrote: > >> Hi: > >> > >> Would it be possible to support interchange floating point and/or > >> extended floating point for C++, which is introduced by ISO/IEC TS > >> 18661-3? > >> > >> I've read the note about C++ support from the initial commit log[1], > >> so I know there is some concern about C++ support for that, is it > >> possible to enable that for C++ like a language extension for C++? > >> > >> The main demand comes from the data type for half-precision, ISO/IEC > >> TS 18661-3 is the only common spec which supports half-precision and > >> both GCC and clang are supported. > >> > >> However it can't be used on C++ for GCC, so it's hard to use that as a > >> workable solution for half-precision data types. > >> > >> Or maybe ISO/IEC JTC1 SC22 WG14 N2016[2] is a better way for > >> half-precision data types? > > See https://wg21.link/p1467 and https://wg21.link/p1467 for the > > relevant C++ proposals. > Isn't that the same link two times ? The difference is smaller than epsilon. Sorry, the second one should be https://wg21.link/p14678