public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sayle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30404] Wrong FORALL result
Date: Tue, 16 Jan 2007 18:15:00 -0000	[thread overview]
Message-ID: <20070116181530.8521.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30404-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from sayle at gcc dot gnu dot org  2007-01-16 18:15 -------
Subject: Bug 30404

Author: sayle
Date: Tue Jan 16 18:15:19 2007
New Revision: 120829

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=120829
Log:
2007-01-16  Roger Sayle  <roger@eyesopen.com>

        PR fortran/30404
        * trans-stmt.c (forall_info): Remove pmask field.
        (gfc_trans_forall_loop): Remove NVAR argument, instead assume that
        NVAR covers all the interation variables in the current forall_info.
        Add an extra OUTER parameter, which specified the loop header in
        which to place mask index initializations.
        (gfc_trans_nested_forall_loop): Remove NEST_FLAG argument.
        Change the semantics of MASK_FLAG to only control the mask in the
        innermost loop.
        (compute_overall_iter_number): Optimize the trivial case of a
        top-level loop having a constant number of iterations.  Update
        call to gfc_trans_nested_forall_loop.  Calculate the number of
        times the inner loop will be executed, not to size of the 
        iteration space.
        (allocate_temp_for_forall_nest_1): Reuse SIZE as BYTESIZE when
        sizeof(type) == 1.  Tidy up.
        (gfc_trans_assign_need_temp): Remove NEST_FLAG argument from calls
        to gfc_trans_nested_forall_loop.
        (gfc_trans_pointer_assign_need_temp): Likewise.
        (gfc_trans_forall_1): Remove unused BYTESIZE, TMPVAR, SIZEVAR and
        LENVAR local variables.  Split mask allocation into a separate
        hunk/pass from mask population.  Use allocate_temp_for_forall_nest
        to allocate the FORALL mask with the correct size.  Update calls
        to gfc_trans_nested_forall_loop.
        (gfc_evaluate_where_mask): Update call to
        gfc_trans_nested_forall_loop.
        (gfc_trans_where_2): Likewise.

        * gfortran.dg/forall_6.f90: New test case.
        * gfortran.dg/dependency_8.f90: Update test to find "temp" array.
        * gfortran.dg/dependency_13.f90: Likewise.


Added:
    trunk/gcc/testsuite/gfortran.dg/forall_6.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-stmt.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gfortran.dg/dependency_13.f90
    trunk/gcc/testsuite/gfortran.dg/dependency_8.f90


-- 


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


  parent reply	other threads:[~2007-01-16 18:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08  9:48 [Bug fortran/30404] New: " dominiq at lps dot ens dot fr
2007-01-08 11:23 ` [Bug fortran/30404] " pault at gcc dot gnu dot org
2007-01-08 12:23 ` pault at gcc dot gnu dot org
2007-01-11 16:56 ` roger at eyesopen dot com
2007-01-11 17:26 ` kargl at gcc dot gnu dot org
2007-01-16 18:15 ` sayle at gcc dot gnu dot org [this message]
2007-01-29  3:27 ` sayle at gcc dot gnu dot org
2007-02-10 16:24 ` [Bug fortran/30404] [4.1 only] " fxcoudert 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=20070116181530.8521.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).