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: Fri, 15 Mar 2013 12:06:00 -0000 [thread overview] Message-ID: <bug-56615-4-k9PSsn7irV@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 --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-03-15 12:05:55 UTC --- Author: burnus Date: Fri Mar 15 12:05:45 2013 New Revision: 196676 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=196676 Log: 2013-03-15 Tobias Burnus <burnus@net-b.de> PR fortran/56615 * trans-intrinsic.c (gfc_conv_intrinsic_transfer): Pack arrays if they are not simply contiguous. 2013-03-15 Tobias Burnus <burnus@net-b.de> PR fortran/56615 * gfortran.dg/transfer_intrinsic_5.f90: New. Added: branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/transfer_intrinsic_5.f90 Modified: branches/gcc-4_7-branch/gcc/fortran/ChangeLog branches/gcc-4_7-branch/gcc/fortran/trans-intrinsic.c branches/gcc-4_7-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2013-03-15 12:06 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 ` [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-14 21:05 ` 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 [this message] 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-k9PSsn7irV@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: linkBe 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).