public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/111956] [14 Regression] Many powerpc platforms do _not_ have support for IEEE754 long double
Date: Tue, 16 Jan 2024 07:40:12 +0000	[thread overview]
Message-ID: <bug-111956-4-sJ0pNOSv2x@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 #15 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Gaius Mulley from comment #14)
> Ah apologies, is it best that I revert:
> 
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;
> h=81d5ca0b9b8431f1bd7a5ec8a2c94f04bb0cf032
> 
> happy to do this in the morning.

I think it might be better to define M2C_LONGREAL_FLOAT128/M2C_LONGREAL_PPC64LE
(whatever they exactly indicate) in terms of the existing

--with-long-double-128
--with-long-double-format

aka the TARGET_DEFAULT_LONG_DOUBLE_128 that's put into the config plus
with_long_double_format (I think that causes TARGET_IEEEQUAD_DEFAULT
to be defined to 1/0, but only for ppc, via config.gcc and tm_defines).

I can't say whether it's better to revert or disable/fix as I can't say
how this for example affects the M2 ABI (like if there was any 'long double'
before this change and what effective type this used).

  parent reply	other threads:[~2024-01-16  7:40 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
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 [this message]
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-sJ0pNOSv2x@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).