public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58146] Array slice bounds checking
Date: Wed, 14 Aug 2013 16:56:00 -0000 [thread overview]
Message-ID: <bug-58146-4-e56IM0tIkH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58146-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58146
Mikael Morin <mikael at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikael at gcc dot gnu.org
--- Comment #4 from Mikael Morin <mikael at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #0)
> neither does it do so with -fcheck=all at runtime:
>
There is no out of bound at run time because the scalarizer sets the loop
bounds according to the array providing the most information; in this case the
constant array of size 3, so that the loop has only 3 iterations.
next prev parent reply other threads:[~2013-08-14 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 6:38 [Bug fortran/58146] New: " tkoenig at gcc dot gnu.org
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 [this message]
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-e56IM0tIkH@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: link
Be 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).