public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/32454] Bounds-check misses overflow of lhs array Date: Thu, 21 Jun 2007 12:34:00 -0000 [thread overview] Message-ID: <20070621123348.7941.qmail@sourceware.org> (raw) In-Reply-To: <bug-32454-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from burnus at gcc dot gnu dot org 2007-06-21 12:33 ------- I forgot to mention: I think this file is valid Fortran 2003 and only invalid Fortran 95. Maybe using: integer, dimension(4) :: y is a better test case. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32454
next prev parent reply other threads:[~2007-06-21 12:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-21 12:26 [Bug fortran/32454] New: " burnus at gcc dot gnu dot org 2007-06-21 12:34 ` burnus at gcc dot gnu dot org [this message] 2007-07-03 10:25 ` [Bug fortran/32454] " fxcoudert at gcc dot gnu dot org 2010-07-01 15:01 ` dominiq at lps dot ens dot fr 2010-07-01 15:16 ` burnus at gcc dot gnu dot org [not found] <bug-32454-4@http.gcc.gnu.org/bugzilla/> 2010-12-29 15:23 ` dfranke 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=20070621123348.7941.qmail@sourceware.org \ --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).