public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/113152] Fortran 2023 half-cycle trigonometric functions Date: Fri, 29 Dec 2023 20:34:38 +0000 [thread overview] Message-ID: <bug-113152-4-wXF01lohRk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113152-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152 --- Comment #10 from anlauf at gcc dot gnu.org --- (In reply to kargl from comment #0) > Created attachment 56949 [details] > patch with implementation Not a review, just a comment: diff --git a/gcc/fortran/simplify.cc b/gcc/fortran/simplify.cc index 87fefe46cfd..4e546ddb8fa 100644 --- a/gcc/fortran/simplify.cc +++ b/gcc/fortran/simplify.cc @@ -30,6 +30,14 @@ along with GCC; see the file COPYING3. If not see #include "constructor.h" #include "version.h" /* For version_string. */ +/* MPFR 4.2.0 introduced half-cycle trigonometric functions, e.g., sinpi(x). + Introduce a macro so older versions of the MPFR can still be used. */ + +#ifdef MPFR_HALF_CYCLE +#undef MPFR_HALF_CYCLE +#endif +#define MPFR_HALF_CYCLE (MPFR_VERSION_MAJOR > 3 && MPFR_VERSION_MINOR > 1) + /* Prototypes. */ This does not look right, as it would exclude e.g. all mpfr-[5-9].[01] How about: #define MPFR_HALF_CYCLE (MPFR_VERSION_MAJOR * 100 + MPFR_VERSION_MINOR >= 402)
next prev parent reply other threads:[~2023-12-29 20:34 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-27 1:24 [Bug fortran/113152] New: " kargl at gcc dot gnu.org 2023-12-27 1:25 ` [Bug fortran/113152] " kargl at gcc dot gnu.org 2023-12-27 1:26 ` kargl at gcc dot gnu.org 2023-12-27 1:27 ` kargl at gcc dot gnu.org 2023-12-27 1:28 ` kargl at gcc dot gnu.org 2023-12-27 10:20 ` mikael at gcc dot gnu.org 2023-12-27 19:16 ` kargl at gcc dot gnu.org 2023-12-27 23:51 ` kargl at gcc dot gnu.org 2023-12-27 23:56 ` kargl at gcc dot gnu.org 2023-12-27 23:57 ` kargl at gcc dot gnu.org 2023-12-29 20:08 ` kargl at gcc dot gnu.org 2023-12-29 20:34 ` anlauf at gcc dot gnu.org [this message] 2023-12-30 0:56 ` sgk at troutmask dot apl.washington.edu 2024-01-20 19:12 ` kargl at gcc dot gnu.org 2024-01-21 21:52 ` anlauf at gcc dot gnu.org 2024-01-21 23:52 ` sgk at troutmask dot apl.washington.edu 2024-01-22 0:10 ` kargl at gcc dot gnu.org 2024-01-22 17:35 ` anlauf at gcc dot gnu.org 2024-01-22 18:06 ` sgk at troutmask dot apl.washington.edu 2024-01-22 18:22 ` anlauf 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-113152-4-wXF01lohRk@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).