public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <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: Wed, 01 Nov 2023 13:52:08 +0000 [thread overview]
Message-ID: <bug-111956-4-bySAGoNxNM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111956-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111956
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #2)
> While you (Gaius) here report test failure, similar to what Maciej had
> reported in PR112091 "rs6000: redefinition of 'constexpr long double
> std::abs(long double)', while building libgm2", I can't even build libgm2
> anymore.
>
> Similar had reported Eric (CCed here) on GCC IRC, 2023-10-20:
>
> <ericgallager> ok now this is an error I haven't seen before
> <ericgallager>
> /home/egallager/gcc/.cfarm135_build.build/powerpc64le-unknown-linux-gnu/
> libstdc++-v3/include/bits/std_abs.h:137:3: error: redefinition of 'constexpr
> long double std::abs(long double)'
> <ericgallager> seen on cfarm135
> <ericgallager> I think I remember something about __float128 being weird
> on certain powerpc systems? Is there a configure flag that affects it?
> <ericgallager> I'll open a bug about it...
> <ericgallager> although actually wait... I'm not quite sure the
> component, though... it's an error from a libstdc++ header, but it shows up
> while building KeyBoardLEDs.lo for libm2cor in libgm2, but only for a
> specific target...
Ah, thanks for the cc! I'd meant to look further into this, but got distracted
by other things...
next prev parent reply other threads:[~2023-11-01 13:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 15:47 [Bug modula2/111956] New: " gaius at gcc dot gnu.org
2023-10-25 23:33 ` [Bug modula2/111956] " pinskia at gcc dot gnu.org
2023-10-31 9:23 ` tschwinge at gcc dot gnu.org
2023-11-01 13:52 ` egallager at gcc dot gnu.org [this message]
2023-11-04 19:11 ` gaius at gcc dot gnu.org
2023-11-04 20:24 ` macro at orcam dot me.uk
2023-11-07 14:12 ` gaius at gcc dot gnu.org
2023-11-07 14:15 ` gaius at gcc dot gnu.org
2023-11-07 14:18 ` gaius at gcc dot gnu.org
2023-11-09 2:29 ` macro at orcam dot me.uk
2023-11-09 7:27 ` tschwinge at gcc dot gnu.org
2023-11-09 10:27 ` tkoenig at gcc dot gnu.org
2023-11-14 16:38 ` gaius at gcc dot gnu.org
2024-01-15 7:36 ` [Bug modula2/111956] [14 Regression] " rguenth at gcc dot gnu.org
2024-01-16 1:05 ` gaius at gcc dot gnu.org
2024-01-16 7:40 ` rguenth at gcc dot gnu.org
2024-01-16 10:22 ` gaiusmod2 at gmail dot com
2024-01-16 14:09 ` rguenth at gcc dot gnu.org
2024-01-17 1:12 ` gaius at gcc dot gnu.org
2024-01-18 0:25 ` gaius at gcc dot gnu.org
2024-01-18 0:29 ` gaius at gcc dot gnu.org
2024-01-18 13:07 ` cvs-commit at gcc dot gnu.org
2024-01-18 16:42 ` gaius 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-111956-4-bySAGoNxNM@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).