public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56615] [4.6/4.7/4.8 Regression] Wrong code with TRANSFER of arrays of character with stride -1
Date: Thu, 14 Mar 2013 18:01:00 -0000	[thread overview]
Message-ID: <bug-56615-4-GAz9zfFdWf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56615-4@http.gcc.gnu.org/bugzilla/>


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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
      Known to work|                            |4.1.2, 4.3.4
           Keywords|                            |wrong-code
   Last reconfirmed|                            |2013-03-14
                 CC|                            |burnus at gcc dot gnu.org
     Ever Confirmed|0                           |1
            Summary|[4.4/4.5/4.6/4.7            |[4.6/4.7/4.8 Regression]
                   |Regression] Wrong code for  |Wrong code with TRANSFER of
                   |passing arrays of character |arrays of character with
                   |                            |stride -1
   Target Milestone|---                         |4.6.4
      Known to fail|                            |4.4.0, 4.5.3, 4.6.3, 4.7.2,
                   |                            |4.8.0

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-03-14 18:01:06 UTC ---
The problem seems to be the TRANSFER in:

  call cmp (a(n:1:-1), t)
...
  subroutine cmp (b, s)
    character(len=1), dimension(:), intent(in) :: b
    c = TRANSFER (b, c)



In the dump, I see code like:

__builtin_memcpy (transfer.5, parm.4.data, MAX_EXPR
<MIN_EXPR<D.1912,D.1904>,0>);


However, that assumes that parm.4.data is contiguous and walked forwardly. In
4.4, one has the same - but additionally the calls:

D.929 = _gfortran_internal_pack (&parm.4);
...
_gfortran_internal_unpack (&parm.4, D.929);


  reply	other threads:[~2013-03-14 18:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 12:10 [Bug fortran/56615] New: [4.4/4.5/4.6/4.7 Regression] Wrong code for passing arrays of character anlauf at gmx dot de
2013-03-14 18:01 ` burnus at gcc dot gnu.org [this message]
2013-03-14 21:05 ` [Bug fortran/56615] [4.6/4.7/4.8 Regression] Wrong code with TRANSFER of arrays of character with stride -1 burnus at gcc dot gnu.org
2013-03-15 10:10 ` burnus at gcc dot gnu.org
2013-03-15 12:06 ` burnus at gcc dot gnu.org
2013-03-15 12:07 ` burnus at gcc dot gnu.org
2013-03-15 12:09 ` burnus 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-56615-4-GAz9zfFdWf@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).