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/113471] [14 regression] wrong array bound check failure on valid code Date: Fri, 19 Jan 2024 20:24:16 +0000 [thread overview] Message-ID: <bug-113471-4-RzYYB664r2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113471-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113471 --- Comment #5 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:94b2e6cb1cc4feb122bf77f19a657c97bffa9b42 commit r14-8295-g94b2e6cb1cc4feb122bf77f19a657c97bffa9b42 Author: Harald Anlauf <anlauf@gmx.de> Date: Fri Jan 19 21:20:44 2024 +0100 Fortran: fix wrong array bounds check [PR113471] gcc/fortran/ChangeLog: PR fortran/113471 * trans-array.cc (array_bound_check_elemental): Array bounds check shall apply here to elemental dimensions of an array section only. gcc/testsuite/ChangeLog: PR fortran/113471 * gfortran.dg/bounds_check_24.f90: New test.
next prev parent reply other threads:[~2024-01-19 20:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 9:34 [Bug fortran/113471] New: " juergen.reuter at desy dot de 2024-01-18 10:49 ` [Bug fortran/113471] " rguenth at gcc dot gnu.org 2024-01-18 18:02 ` anlauf at gcc dot gnu.org 2024-01-18 19:44 ` anlauf at gcc dot gnu.org 2024-01-18 22:12 ` juergen.reuter at desy dot de 2024-01-18 22:19 ` anlauf at gcc dot gnu.org 2024-01-19 20:24 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-19 22:14 ` 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-113471-4-RzYYB664r2@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).