public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/48477] [4.7 Regression]: gfortran.dg/coarray_13.f90 Date: Wed, 06 Apr 2011 13:04:00 -0000 [thread overview] Message-ID: <bug-48477-4-Pab5ovOPAQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48477-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48477 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2011.04.06 13:04:07 Ever Confirmed|0 |1 --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-04-06 13:04:07 UTC --- Confirm on x86-64-Linux. In a way I am surprised that it does not crash there - but at least valgrind properly warns. The issue is: allocate(B(3)[-4:*]) call three_b(3,B) ... subroutine three_b(n,A) integer :: n integer :: A(-1:3,0:4,-2:5,-4:7)[n+2:n+5,n-1:*] ... A(1,1,1,1) = 42 Thus, one passes "B" which is a size 3 array as actual argument to a dummy array "A" which has the size 2400. (That's questionable usage, but still valid.) If one now accesses the element A(1,1,1,1) on effectively accesses array element B(144) which is not that healthy if B has only 3 elements.
next prev parent reply other threads:[~2011-04-06 13:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-06 6:50 [Bug regression/48477] New: " hp at gcc dot gnu.org 2011-04-06 10:10 ` [Bug regression/48477] " rguenth at gcc dot gnu.org 2011-04-06 13:04 ` burnus at gcc dot gnu.org [this message] 2011-04-06 18:32 ` burnus at gcc dot gnu.org 2011-04-06 22:51 ` burnus at gcc dot gnu.org 2011-04-07 0:18 ` hp 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-48477-4-Pab5ovOPAQ@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).