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/37903] [4.3/4.4 Regression] wrong-code for complicated vector subscripts
Date: Sat, 01 Nov 2008 19:48:00 -0000	[thread overview]
Message-ID: <20081101194708.19305.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37903-14266@http.gcc.gnu.org/bugzilla/>



------- Comment #16 from pault at gcc dot gnu dot org  2008-11-01 19:47 -------
Subject: Bug 37903

Author: pault
Date: Sat Nov  1 19:45:41 2008
New Revision: 141521

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=141521
Log:
2008-11-01  Mikael Morin  <mikael.morin@tele2.fr>

        PR fortran/37903
        * trans-array.c (gfc_trans_create_temp_array): If n is less
        than the temporary dimension, assert that loop->from is
        zero (reverts to earlier versions). If there is at least one
        null loop->to[n], it is a callee allocated array so set the
        size to NULL and break.
        (gfc_trans_constant_array_constructor): Set the offset to zero.
        (gfc_trans_array_constructor): Remove loop shifting around the
        temporary creation.
        (gfc_conv_loop_setup): Prefer zero-based descriptors if
        possible.  Calculate the translation from loop variables to
        array indices if an array constructor.

2008-11-01  Mikael Morin  <mikael.morin@tele2.fr>

        PR fortran/37749
        * trans-array.c (gfc_trans_create_temp_array): If size is NULL
        use the array bounds for loop->to.

2008-11-01  Mikael Morin  <mikael.morin@tele2.fr>

        PR fortran/37903
        * gfortran.dg/vector_subscript_4.f90: New test.

2008-11-01  Mikael Morin  <mikael.morin@tele2.fr>

        PR fortran/37749
        * gfortran.dg/vector_subscript__5.f90: New test.

Added:
    branches/gcc-4_3-branch/gcc/testsuite/gfortran.dg/vector_subscript_4.f90
    branches/gcc-4_3-branch/gcc/testsuite/gfortran.dg/vector_subscript_5.f90
Modified:
    branches/gcc-4_3-branch/gcc/fortran/ChangeLog
    branches/gcc-4_3-branch/gcc/fortran/trans-array.c
    branches/gcc-4_3-branch/gcc/testsuite/ChangeLog


-- 


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


  parent reply	other threads:[~2008-11-01 19:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 18:49 [Bug fortran/37903] New: " mikael dot morin at tele2 dot fr
2008-10-23 20:13 ` [Bug fortran/37903] [4.3/4.4 Regression] " burnus at gcc dot gnu dot org
2008-10-23 20:31 ` dominiq at lps dot ens dot fr
2008-10-23 21:28 ` mikael dot morin at tele2 dot fr
2008-10-23 22:32 ` mikael dot morin at tele2 dot fr
2008-10-24  5:49 ` dominiq at lps dot ens dot fr
2008-10-24 11:34 ` rguenth at gcc dot gnu dot org
2008-10-25 21:05 ` jakub at gcc dot gnu dot org
2008-10-28  6:26 ` pault at gcc dot gnu dot org
2008-10-28 12:22 ` mikael dot morin at tele2 dot fr
2008-10-28 14:44 ` mikael dot morin at tele2 dot fr
2008-10-28 17:20 ` dominiq at lps dot ens dot fr
2008-10-28 18:28 ` mikael dot morin at tele2 dot fr
2008-10-28 18:44 ` mikael dot morin at tele2 dot fr
2008-10-28 18:47 ` domob at gcc dot gnu dot org
2008-10-30 11:08 ` pault at gcc dot gnu dot org
2008-10-30 20:50 ` pault at gcc dot gnu dot org
2008-11-01 19:48 ` pault at gcc dot gnu dot org [this message]
2008-11-01 19:48 ` 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=20081101194708.19305.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).