public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109511] incorrectly rejects set_exponent with constant negative exponent Date: Sun, 16 Apr 2023 18:52:52 +0000 [thread overview] Message-ID: <bug-109511-4-dk0jew0UKF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109511-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109511 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:dfcdb457c462b9e35eb54d3b758221a119067e24 commit r11-10625-gdfcdb457c462b9e35eb54d3b758221a119067e24 Author: Harald Anlauf <anlauf@gmx.de> Date: Fri Apr 14 20:45:19 2023 +0200 Fortran: fix compile-time simplification of SET_EXPONENT [PR109511] gcc/fortran/ChangeLog: PR fortran/109511 * simplify.c (gfc_simplify_set_exponent): Fix implementation of compile-time simplification of intrinsic SET_EXPONENT for argument X < 1 and for I < 0. gcc/testsuite/ChangeLog: PR fortran/109511 * gfortran.dg/set_exponent_1.f90: New test. (cherry picked from commit fa4cb42870df60deb8888dbd51e2ddc6d6ab9e6a)
next prev parent reply other threads:[~2023-04-16 18:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-14 9:52 [Bug fortran/109511] New: " sebastien at debian dot org 2023-04-14 11:54 ` [Bug fortran/109511] " anlauf at gcc dot gnu.org 2023-04-14 17:19 ` anlauf at gcc dot gnu.org 2023-04-14 17:36 ` anlauf at gcc dot gnu.org 2023-04-14 19:01 ` anlauf at gcc dot gnu.org 2023-04-14 19:23 ` sebastien at debian dot org 2023-04-14 19:51 ` cvs-commit at gcc dot gnu.org 2023-04-15 13:44 ` cvs-commit at gcc dot gnu.org 2023-04-16 18:52 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-16 19:01 ` cvs-commit at gcc dot gnu.org 2023-04-16 19:02 ` 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-109511-4-dk0jew0UKF@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).