From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 1BE8E3895FEF; Tue, 15 Nov 2022 14:27:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1BE8E3895FEF
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1668522459;
	bh=Vw2yxQESRm0q3U5GinQCgCVue5ouIhh0YdgkJZi35zI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ngRYhAo8RpaRCzqSOQw9UFfRuUjNlaP02eOuzqtYDCK2wjPycvrA9mZS+yAyCjkiK
	 G2pSk+J0jWskPdwYCSkW/P31bSqD0AV4oNnOauz2lg/z0AipRtj762D5En+SoMkFuG
	 SNOcymx7QSXmkqx403GCL3JOxzTp0kbBLcmeCCdw=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107665] g++.dg/cpp23/ext-floating1.C fails after
 r13-3387-g79d38dd46e6b07
Date: Tue, 15 Nov 2022 14:27:38 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107665-4-tUMYs0OwRu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107665-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107665-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107665

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Strange.
When I try with a cross to powerpc64le-linux simplified:
namespace std
{
  template<typename T, T v> struct integral_constant {
    static constexpr T value =3D v;
  };
  typedef integral_constant<bool, false> false_type;
  typedef integral_constant<bool, true> true_type;
  template<class T, class U>
  struct is_same : std::false_type {};
  template <class T>
  struct is_same<T, T> : std::true_type {};
}

static_assert (std::is_same<decltype (0.0q), __float128>::value);
out of this, I get with any of
-std=3Dgnu++23 -mlong-double-{64,128 -mabi=3D{ieee,ibm}longdouble}
a successful compilation.
So, what type do you get instead?
static machine_mode
rs6000_c_mode_for_suffix (char suffix)
{
  if (TARGET_FLOAT128_TYPE)
    {
      if (suffix =3D=3D 'q' || suffix =3D=3D 'Q')
        return (FLOAT128_IEEE_P (TFmode)) ? TFmode : KFmode;

      /* At the moment, we are not defining a suffix for IBM extended doubl=
e.
         If/when the default for -mabi=3Dieeelongdouble is changed, and we =
want
         to support __ibm128 constants in legacy library code, we may need =
to
         re-evalaute this decision.  Currently, c-lex.cc only supports 'w' =
and
         'q' as machine dependent suffixes.  The x86_64 port uses 'w' for
         __float80 constants.  */
    }

  return VOIDmode;
}=20=20=20
should return TFmode or KFmode and the c-family code should prefer
float128t_type_node over float128_type_node for the q/w suffixes.=