public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "macro at orcam dot me.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/112091] New: rs6000: redefinition of 'constexpr long double std::abs(long double)', while building libgm2
Date: Wed, 25 Oct 2023 23:31:41 +0000 [thread overview]
Message-ID: <bug-112091-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112091
Bug ID: 112091
Summary: rs6000: redefinition of 'constexpr long double
std::abs(long double)', while building libgm2
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: build
Severity: normal
Priority: P3
Component: modula2
Assignee: gaius at gcc dot gnu.org
Reporter: macro at orcam dot me.uk
Target Milestone: ---
Target: powerpc64le-linux-gnu
As from commit 81d5ca0b9b84 ("PR 108143/modula2 LONGREAL and
powerpc64le-linux") target libgm2 fails building in a native
`powerpc64le-linux-gnu' bootstrap with system glibc 2.28:
cc1plus: warning: Using IEEE extended precision 'long double' [-Wpsabi]
In file included from
.../powerpc64le-linux-gnu/libstdc++-v3/include/cstdlib:81,
from
.../powerpc64le-linux-gnu/libstdc++-v3/include/stdlib.h:36,
from .../libgm2/libm2cor/KeyBoardLEDs.cc:43:
.../powerpc64le-linux-gnu/libstdc++-v3/include/bits/std_abs.h:137:3: error:
redefinition of 'constexpr long double std::abs(long double)'
137 | abs(__float128 __x)
| ^~~
.../powerpc64le-linux-gnu/libstdc++-v3/include/bits/std_abs.h:79:3: note:
'constexpr long double std::abs(long double)' previously defined here
79 | abs(long double __x)
| ^~~
make[5]: *** [Makefile:818: KeyBoardLEDs.lo] Error 1
This is apparently because with the `-mabi=ieeelongdouble' compilation
option used in this configuration we assume the redirection of the
`long double' data type to `__float128' and it is only supported by
glibc as from commit 051be01f6b41 ("powerpc64le: Enable support for IEEE
long double") or released version 2.32.
It is not clear to me what the correct solution to this issue would be
for glibc < 2.32, i.e. whether we ought to bail out gracefully such as
by disabling LONGREAL support, or even the frontend entirely, or whether
we could use explicit `__float128' data type rather than `long double'.
I guess in the latter case there might be ABI consequences, so it would
have to be considered carefully. Input from someone more familiar with
the intricacies of the 64-bit POWER ABI might be desirable.
Relevant glibc mailing list discussion threads:
https://sourceware.org/pipermail/libc-alpha/2020-February/111092.html
https://sourceware.org/pipermail/libc-alpha/2020-March/112248.html
https://sourceware.org/pipermail/libc-alpha/2020-April/112579.html
next reply other threads:[~2023-10-25 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 23:31 macro at orcam dot me.uk [this message]
2023-10-25 23:33 ` [Bug modula2/112091] " pinskia at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-112091-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).