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 5979A3858D3C; Sat,  4 Nov 2023 20:24:51 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5979A3858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1699129491;
	bh=riT3BCEi5MJenWMGcolW72Y8j5HIjbZou7nEJUtjrYM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=iMrFUALpZhNhu+4q5nGLUndK1yUpfhSv5znZX+QvOyXXXzXcb13YduMoiVVogc6t4
	 nCi1dc9E904hptPJfU6l2pw9Q9Zk+05OW1Odmn3tcJU1iySA5VPDwBq13i3aFYgCO0
	 UY0dtdhSmJwa9l9vHQWgxJK7hCkMtWuhWk1Z7tRY=
From: "macro at orcam dot me.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/111956] Many powerpc platforms do _not_ have support
 for IEEE754 long double
Date: Sat, 04 Nov 2023 20:24:50 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: modula2
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: macro at orcam dot me.uk
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: gaius at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-111956-4-C26uSH2U9M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111956-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111956-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=3D111956

--- Comment #5 from Maciej W. Rozycki <macro at orcam dot me.uk> ---
Hmm, this seems awkward to me.  It won't work AFAICT with the usual
native bootstrap environment, where you just run:

$ /path/to/configure && make bootstrap

and it won't work where you have an old version of glibc installed
and build with:

$ /path/to/configure --with-cpu=3Dpower10 && make bootstrap

either.  Shouldn't this just use the same check that libstdc++ does?
See the piece starting with:

# Check for IEEE128 support in libm.

in libstdc++-v3/configure.ac.  Maybe you just need to check for the
presence of `__frexpieee128' and ignore the rest, as you don't seem
to be willing to provide support for the IBM long double format in
libgm2, or do you?=