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/103707] Stray "Array operands are incommensurate" Date: Wed, 06 Mar 2024 16:57:17 +0000 [thread overview] Message-ID: <bug-103707-4-nRi3NfrkHu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103707-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103707 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:93e1d4d24ed014387da97e2ce11556d68fe98e66 commit r14-9340-g93e1d4d24ed014387da97e2ce11556d68fe98e66 Author: Harald Anlauf <anlauf@gmx.de> Date: Tue Mar 5 21:54:26 2024 +0100 Fortran: error recovery while simplifying expressions [PR103707,PR106987] When an exception is encountered during simplification of arithmetic expressions, the result may depend on whether range-checking is active (-frange-check) or not. However, the code path in the front-end should stay the same for "soft" errors for which the exception is triggered by the check, while "hard" errors should always terminate the simplification, so that error recovery is independent of the flag. Separation of arithmetic error codes into "hard" and "soft" errors shall be done consistently via is_hard_arith_error(). PR fortran/103707 PR fortran/106987 gcc/fortran/ChangeLog: * arith.cc (is_hard_arith_error): New helper function to determine whether an arithmetic error is "hard" or not. (check_result): Use it. (gfc_arith_divide): Set "Division by zero" only for regular numerators of real and complex divisions. (reduce_unary): Use is_hard_arith_error to determine whether a hard or (recoverable) soft error was encountered. Terminate immediately on hard error, otherwise remember code of first soft error. (reduce_binary_ac): Likewise. (reduce_binary_ca): Likewise. (reduce_binary_aa): Likewise. gcc/testsuite/ChangeLog: * gfortran.dg/pr99350.f90: * gfortran.dg/arithmetic_overflow_3.f90: New test.
next prev parent reply other threads:[~2024-03-06 16:57 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-14 10:28 [Bug fortran/103707] New: " tkoenig at gcc dot gnu.org 2021-12-14 10:30 ` [Bug fortran/103707] " tkoenig at gcc dot gnu.org 2021-12-14 16:07 ` anlauf at gcc dot gnu.org 2021-12-14 18:16 ` gscfq@t-online.de 2021-12-14 18:27 ` gscfq@t-online.de 2021-12-15 7:58 ` tkoenig at gcc dot gnu.org 2022-06-26 21:21 ` anlauf at gcc dot gnu.org 2024-03-06 16:57 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-06 21:33 ` anlauf at gcc dot gnu.org 2024-04-02 17:07 ` cvs-commit at gcc dot gnu.org 2024-04-02 17:33 ` 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-103707-4-nRi3NfrkHu@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).