public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge 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: Thu, 09 Nov 2023 07:27:47 +0000 [thread overview] Message-ID: <bug-111956-4-P8Oo0ANzoF@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 #10 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- In addition to what Maciej said (..., and similarly, I don't have any proper knowledge about PowerPC details): (In reply to Gaius Mulley from comment #6) > Created attachment 56522 [details] > Proposed fix v5 Thanks for looking into this! > Here is the latest patch which [...] 96 > failures on gcc135. [...] With no special 'configure' flags, I'm seeing (presumably) those, too. I noticed in 'build-gcc/gcc/m2/config-make' (generated from 'gcc/m2/config-make.in'): # Does the target have -mabi=ieeelongdouble support in libm? (yes/no). HAVE_TARGET_LONG_DOUBLE_IEEE = @have_target_long_double_ieee@ ..., so missing 'AC_SUBST' or similar -- but is that actually unused? I further noticed the following delta when regenerating 'libgm2/configure': case "$target" in powerpc*-*-linux*) - LONG_DOUBLE_COMPAT_FLAGS="$LONG_DOUBLE_COMPAT_FLAGS -mno-gnu-attribute" # Check for IEEE128 support in libm: (In reply to Gaius Mulley from comment #8) > Here is the same patch as v5 but generated using git diff -w. Please don't include unrelated changes (here: whitespace cleanup); handle that separately (if you must). ;-)
next prev parent reply other threads:[~2023-11-09 7:27 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 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 [this message] 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-P8Oo0ANzoF@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: linkBe 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).