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/113245] New: SIZE with optional DIM argument that has the OPTIONAL+VALUE attributes Date: Fri, 05 Jan 2024 19:31:08 +0000 [thread overview] Message-ID: <bug-113245-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113245 Bug ID: 113245 Summary: SIZE with optional DIM argument that has the OPTIONAL+VALUE attributes Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: anlauf at gcc dot gnu.org Target Milestone: --- Related to pr30865, but with optional that has the VALUE attribute. Testcase: program p implicit none real :: a(2,3) call ref (a,2) ! works call val (a,2) ! works print *, "--" call ref (a) ! works call val (a) ! fails contains subroutine ref (x, d) real, intent(in) :: x(:,:) integer, optional, intent(in) :: d print *, "present (d) =", present (d) print *, "size (a, d) =", size (x, dim=d) end subroutine val (x, d) real, intent(in) :: x(:,:) integer, optional, value :: d print *, "present (d) =", present (d) print *, "size (a, d) =", size (x, dim=d) ! <<< miscompiled end end The dump-tree shows that the presence test is miscompiled, leading to always accessing 'd', which is 0 for an absent argument, and causing an invalid access.
next reply other threads:[~2024-01-05 19:31 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-05 19:31 anlauf at gcc dot gnu.org [this message] 2024-01-05 19:31 ` [Bug fortran/113245] " anlauf at gcc dot gnu.org 2024-01-07 20:26 ` anlauf at gcc dot gnu.org 2024-01-07 21:35 ` anlauf at gcc dot gnu.org 2024-01-08 17:50 ` cvs-commit at gcc dot gnu.org 2024-01-08 20:45 ` 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-113245-4@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).