public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/58146] New: Array slice bounds checking Date: Tue, 13 Aug 2013 06:38:00 -0000 [thread overview] Message-ID: <bug-58146-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58146 Bug ID: 58146 Summary: Array slice bounds checking Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: tkoenig at gcc dot gnu.org The following doesn't trigger an error at compile time, neither does it do so with -fcheck=all at runtime: ig25@linux-fd1f:/tmp> cat diff.f90 program main implicit none integer :: n real, dimension(10) :: a n = 0 call random_number(a) if (any(a(n+1:n+4) > [1.0, 2.0, 3.0])) print *,"Hello!" end program main ig25@linux-fd1f:/tmp> gfortran -fcheck=all diff.f90 ig25@linux-fd1f:/tmp> ./a.out ig25@linux-fd1f:/tmp>
next reply other threads:[~2013-08-13 6:38 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-13 6:38 tkoenig at gcc dot gnu.org [this message] 2013-08-13 6:38 ` [Bug fortran/58146] " tkoenig at gcc dot gnu.org 2013-08-13 14:15 ` dominiq at lps dot ens.fr 2013-08-13 22:08 ` tkoenig at gcc dot gnu.org 2013-08-13 22:55 ` tkoenig at gcc dot gnu.org 2013-08-14 16:56 ` mikael at gcc dot gnu.org 2013-08-14 17:06 ` mikael at gcc dot gnu.org 2013-08-14 21:26 ` tkoenig at gcc dot gnu.org 2013-08-27 9:52 ` mikael at gcc dot gnu.org 2013-08-27 11:31 ` mikael at gcc dot gnu.org 2013-08-27 17:26 ` tkoenig at gcc dot gnu.org 2023-09-18 21:37 ` 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-58146-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).