public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anthony.debeus at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/97039] -fbounds-check misses violation with slice of array but not an element Date: Thu, 15 Oct 2020 23:00:23 +0000 [thread overview] Message-ID: <bug-97039-4-eK7HdJeCNH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97039-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97039 --- Comment #2 from Anthony M de Beus <anthony.debeus at gmail dot com> --- Clarification for anyone confused, "correct" results by a fortran compiler with bounds-checking enabled would include finding/checking incorrect bounds in (deliberately) incorrect fortran code given in the illustrative example. Hence in the example given, the pgf90 v.20.7 compiler correctly identifies the incorrect fortran code involving the array slice, whereas the gfortran compiler only catches the second error in the code, involving a specific element, but not the first error, involving a slice.
next prev parent reply other threads:[~2020-10-15 23:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-13 15:04 [Bug fortran/97039] New: " anthony.debeus at gmail dot com 2020-09-13 16:35 ` [Bug fortran/97039] " kargl at gcc dot gnu.org 2020-10-15 23:00 ` anthony.debeus at gmail dot com [this message] 2020-10-16 20:43 ` anlauf at gcc dot gnu.org 2023-09-15 18:21 ` 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-97039-4-eK7HdJeCNH@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).