From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by sourceware.org (Postfix) with ESMTPS id 4B7EA388C00F for ; Thu, 11 Mar 2021 14:02:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 4B7EA388C00F Received: by mail-wr1-x436.google.com with SMTP id h98so1972708wrh.11 for ; Thu, 11 Mar 2021 06:02:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=IkL1x7F03q+Be57aQukQJTKMbbGqXy2tW4KuVSnRkBI=; b=h6CU5aZrcV2ro9WLogHHdc3uMsbmXcNzDqxbgCt+HexSbYMVsHq0xrYvgmbAGK171e h4vSxJmJcz1UYDbe+4GTUzDaofWpjPUUrukcUZ2Cj/sYptKGCUj5yGrryqXEBHUjLJGt cQo2BEHZTl9fck3eNrwg2u1yfFAf6M13HK6bgf9Z8q9OiC5yPdmqzifpFBIkJGEecy+3 v8NQQ74GdZmbh2ipdRb1jMIp/ZNLQQPxiQZyLDOzgpXNnQfoWEXLO6br0JNe2GW53Rdj ks21XY3ZwxxOO9HSypqgUaslQ8BCYg0UR4oEQ0mN5hR3k8ap4jNYwd2ROB8suS96064r zHWA== X-Gm-Message-State: AOAM531lIJgccAvBmSUc0o2g6A5wSUxLBDJ/u7enzJYTBkDB258KQ/k8 8Uyv2y9mZpRH1vEvoZf2XUPVTCadx4OO/A== X-Google-Smtp-Source: ABdhPJzC77TBcH8ohF1xDY9pRuOkEshPehzUzVQEAx3HmyvKaWPfCVDDNoFpeS0eXFWxsINo8rbY4A== X-Received: by 2002:a5d:6304:: with SMTP id i4mr8824750wru.155.1615471351263; Thu, 11 Mar 2021 06:02:31 -0800 (PST) Received: from [10.18.0.7] ([188.241.83.110]) by smtp.gmail.com with ESMTPSA id j16sm19597219wmi.2.2021.03.11.06.02.30 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 Mar 2021 06:02:30 -0800 (PST) Subject: Re: IEEE Interchange floating point and extended floating point for C++ To: gcc@gcc.gnu.org References: From: Gabriel Ravier Message-ID: <8bf4aad6-390d-3735-5c8c-457f036c379f@gmail.com> Date: Thu, 11 Mar 2021 15:02:29 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, NICE_REPLY_A, 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 14:02:34 -0000 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 ?