public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/40551] Wrong code due to missing copy-in/copy-out stried array to assumed-size dummy Date: Sun, 05 Jul 2009 19:06:00 -0000 [thread overview] Message-ID: <20090705190619.27474.qmail@sourceware.org> (raw) In-Reply-To: <bug-40551-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from pault at gcc dot gnu dot org 2009-07-05 19:06 ------- Subject: Bug 40551 Author: pault Date: Sun Jul 5 19:06:05 2009 New Revision: 149261 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149261 Log: 2009-07-05 Paul Thomas <pault@gcc.gnu.org> PR fortran/40551 * dependency.h : Add second bool* argument to prototype of gfc_full_array_ref_p. * dependency.c (gfc_full_array_ref_p): If second argument is present, return true if last dimension of reference is an element or has unity stride. * trans-array.c : Add NULL second argument to references to gfc_full_array_ref_p. * trans-expr.c : The same, except for; (gfc_trans_arrayfunc_assign): Return fail if lhs reference is not a full array or a contiguous section. 2009-07-05 Paul Thomas <pault@gcc.gnu.org> PR fortran/40551 * gfortran.dg/func_assign_2.f90 : New test. Added: branches/gcc-4_4-branch/gcc/testsuite/gfortran.dg/func_assign_2.f90 Modified: branches/gcc-4_4-branch/gcc/fortran/ChangeLog branches/gcc-4_4-branch/gcc/fortran/dependency.c branches/gcc-4_4-branch/gcc/fortran/dependency.h branches/gcc-4_4-branch/gcc/fortran/trans-array.c branches/gcc-4_4-branch/gcc/fortran/trans-expr.c branches/gcc-4_4-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40551
next prev parent reply other threads:[~2009-07-05 19:06 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-25 13:30 [Bug fortran/40551] New: " burnus at gcc dot gnu dot org 2009-06-25 13:32 ` [Bug fortran/40551] " burnus at gcc dot gnu dot org 2009-06-25 14:22 ` dominiq at lps dot ens dot fr 2009-06-25 15:06 ` burnus at gcc dot gnu dot org 2009-06-25 15:43 ` burnus at gcc dot gnu dot org 2009-06-25 16:05 ` burnus at gcc dot gnu dot org 2009-06-28 20:31 ` pault at gcc dot gnu dot org 2009-06-29 9:21 ` pault at gcc dot gnu dot org 2009-06-29 15:19 ` pault at gcc dot gnu dot org 2009-06-29 20:39 ` pault at gcc dot gnu dot org 2009-06-30 6:24 ` pault at gcc dot gnu dot org 2009-07-05 19:06 ` pault at gcc dot gnu dot org [this message] 2009-07-07 12:47 ` burnus at gcc dot gnu dot org 2009-07-07 15:27 ` burnus at gcc dot gnu dot org 2009-07-09 17:06 ` [Bug fortran/40551] Optimizations possible using gfc_full_array_ref_p pault at gcc dot gnu dot org 2009-07-09 17:11 ` pault at gcc dot gnu dot 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=20090705190619.27474.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).