public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107745] long double constexprs don't work with * or /, but work with + and - (JUST ON PPC)
Date: Tue, 20 Feb 2024 15:14:21 +0000 [thread overview]
Message-ID: <bug-107745-4-OrpkUfKiCE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107745-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107745
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at gcc dot gnu.org
--- Comment #6 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Sebastian "spaetz" Spaeth from comment #5)
> I fully understand that nobody wants to invest time into fixing this. What
> would be nice though, is if this were really just a missed optimization and
> not rejecting to compile valid code.
>
> powerpc could ignore the constexpr in this case, rather than failing to
> build?
It will be an violation of the standard (at least in some cases).
next prev parent reply other threads:[~2024-02-20 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 8:50 [Bug c++/107745] New: " Sebastian at SSpaeth dot de
2022-11-18 9:00 ` [Bug c++/107745] " schwab@linux-m68k.org
2022-11-18 9:07 ` Sebastian at SSpaeth dot de
2022-11-18 9:14 ` pinskia at gcc dot gnu.org
2022-11-18 9:19 ` jakub at gcc dot gnu.org
2022-11-18 9:36 ` Sebastian at SSpaeth dot de
2024-02-20 15:14 ` xry111 at gcc dot gnu.org [this message]
2024-02-20 15:26 ` iains at gcc dot gnu.org
2024-02-20 17:19 ` redi 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-107745-4-OrpkUfKiCE@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).