public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47348] wrong string length with array constructor
Date: Sat, 19 Feb 2011 15:11:00 -0000	[thread overview]
Message-ID: <bug-47348-4-eOVNdVFRq5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47348-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> 2011-02-19 15:03:30 UTC ---
Author: pault
Date: Sat Feb 19 15:03:27 2011
New Revision: 170317

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=170317
Log:
2011-02-19  Paul Thomas  <pault@gcc.gnu.org>

    PR fortran/47348
    * trans-array.c (get_array_ctor_all_strlen): Move up in file.
    (get_array_ctor_var_strlen): Add block dummy and add call to
    get_array_ctor_all_strlen instead of giving up on substrings.
    Call gcc_unreachable for default case.
    (get_array_ctor_strlen): Add extra argument to in call to
    get_array_ctor_var_strlen.

2011-02-19  Paul Thomas  <pault@gcc.gnu.org>

    PR fortran/47348
    * gfortran.dg/array_constructor_36.f90 : New test.
    * gfortran.dg/bounds_check_10.f90 : Change dg-output message to
    allow for comparison between different elements of the array
    constructor at different levels of optimization.


Added:
    trunk/gcc/testsuite/gfortran.dg/array_constructor_36.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-array.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gfortran.dg/bounds_check_10.f90


  parent reply	other threads:[~2011-02-19 15:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 18:45 [Bug fortran/47348] New: substring with len_trim in " tkoenig at gcc dot gnu.org
2011-01-18 19:15 ` [Bug fortran/47348] " kargl at gcc dot gnu.org
2011-01-18 20:43 ` tkoenig at gcc dot gnu.org
2011-01-19 19:45 ` [Bug fortran/47348] wrong string length with " tkoenig at gcc dot gnu.org
2011-01-20  9:19 ` tkoenig at gcc dot gnu.org
2011-01-22 17:48 ` paul.richard.thomas at gmail dot com
2011-02-19 15:11 ` pault at gcc dot gnu.org [this message]
2011-02-21 10:38 ` dominiq at lps dot ens.fr
2011-02-21 12:10 ` pault at gcc dot gnu.org
2011-02-21 22:49 ` tkoenig at netcologne dot de
2011-03-13 17:38 ` pault at gcc dot gnu.org
2011-03-13 17:41 ` pault 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-47348-4-eOVNdVFRq5@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).