public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60322] [OOP] Incorrect bounds on polymorphic dummy array
Date: Sun, 23 Feb 2014 11:21:00 -0000	[thread overview]
Message-ID: <bug-60322-4-hSy9ewdK5O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60322-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from janus at gcc dot gnu.org ---
For both cases (TYPE and CLASS), the temporary that is created (to be passed to
copyFromArray) has an lbound of zero (as shown by -fdump-tree-original):

    atmp.6.dim[0].stride = 1;
    atmp.6.dim[0].lbound = 0;
    atmp.6.dim[0].ubound = 0;

For the TYPE case, additional code (and another temporary) is generated inside
of copyFromArray, which resets the bounds:

            parm.6.dim[0].lbound = 1;
            parm.6.dim[0].ubound = D.2342;

So we just have to make sure that this additional code is also generated for
the CLASS case.

Or, why not directly start with lbound=1 for the original temporary?


  parent reply	other threads:[~2014-02-23 11:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23  3:00 [Bug fortran/60322] New: " Thomas.L.Clune at nasa dot gov
2014-02-23 10:51 ` [Bug fortran/60322] [OOP] " janus at gcc dot gnu.org
2014-02-23 11:21 ` janus at gcc dot gnu.org [this message]
2014-02-23 11:28 ` janus at gcc dot gnu.org
2014-03-13 22:41 ` dominiq at lps dot ens.fr
2015-01-20 16:53 ` antony at cosmologist dot info
2015-01-21 13:32 ` vehre at gmx dot de
2015-01-23 11:14 ` vehre at gcc dot gnu.org
2015-01-29 10:32 ` vehre at gcc dot gnu.org
2015-04-23 11:32 ` vehre at gcc dot gnu.org
2015-04-27 17:41 ` vehre at gcc dot gnu.org
2015-05-04 15:11 ` vehre at gcc dot gnu.org
2015-05-10 13:40 ` mikael at gcc dot gnu.org
2015-09-12 23:34 ` dominiq at lps dot ens.fr

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-60322-4-hSy9ewdK5O@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).