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/28174] Corruption of multiple character arrays when passing array sections
Date: Thu, 06 Jul 2006 15:35:00 -0000	[thread overview]
Message-ID: <20060706153534.20740.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28174-6318@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from pault at gcc dot gnu dot org  2006-07-06 15:35 -------
Subject: Bug 28174

Author: pault
Date: Thu Jul  6 15:35:24 2006
New Revision: 115222

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115222
Log:
2006-07-06  Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/28174
        * trans-array.c (gfc_conv_expr_descriptor): When building temp,
        ensure that the substring reference uses a new charlen.
        * trans-expr.c (gfc_conv_aliased_arg): Add the formal intent to
        the argument list, lift the treatment of missing string lengths
        from the above and implement the use of the intent.
        (gfc_conv_function_call): Add the extra argument to the call to
        the above.

        PR fortran/28167
        * trans-array.c (get_array_ctor_var_strlen): Treat a constant
        substring reference.
        * array.c (gfc_resolve_character_array_constructor): Remove 
        static attribute and add the gfc_ prefix, make use of element
        charlens for the expression and pick up constant string lengths
        for expressions that are not themselves constant.
        * gfortran.h : resolve_character_array_constructor prototype
        added.
        * resolve.c (gfc_resolve_expr): Call resolve_character_array_
        constructor again after expanding the constructor, to ensure
        that the character length is passed to the expression.

2006-07-06  Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/28174
        * gfortran.dg/actual_array_substr_2.f90: New test.

        PR fortran/28167
        * gfortran.dg/actual_array_constructor_2.f90: New test.


Modified:
    branches/gcc-4_1-branch/gcc/fortran/ChangeLog
    branches/gcc-4_1-branch/gcc/fortran/array.c
    branches/gcc-4_1-branch/gcc/fortran/gfortran.h
    branches/gcc-4_1-branch/gcc/fortran/resolve.c
    branches/gcc-4_1-branch/gcc/fortran/trans-array.c
    branches/gcc-4_1-branch/gcc/fortran/trans-expr.c
    branches/gcc-4_1-branch/gcc/testsuite/ChangeLog


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28174


  parent reply	other threads:[~2006-07-06 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 20:58 [Bug fortran/28174] New: " anlauf at gmx dot de
2006-06-26 21:01 ` [Bug fortran/28174] " anlauf at gmx dot de
2006-06-27 20:13 ` pault at gcc dot gnu dot org
2006-06-29 22:14 ` patchapp at dberlin dot org
2006-06-30  0:08 ` pault at gcc dot gnu dot org
2006-07-04 20:16 ` pault at gcc dot gnu dot org
2006-07-04 20:36 ` pault at gcc dot gnu dot org
2006-07-06 15:35 ` pault at gcc dot gnu dot org [this message]
2006-07-06 15:37 ` pault at gcc dot gnu dot org
2006-07-13  5:07 ` 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=20060706153534.20740.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: 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).