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/53685] surprising warns about transfer with explicit character range
Date: Sun, 17 Jun 2012 19:31:00 -0000	[thread overview]
Message-ID: <bug-53685-4-o3gMQtX2u3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53685-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-06-17 19:30:44 UTC ---
Author: burnus
Date: Sun Jun 17 19:30:29 2012
New Revision: 188708

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188708
Log:
2012-06-17  Tobias Burnus  <burnus@net-b.de>

        PR fortran/53691
        PR fortran/53685
        * check.c (gfc_calculate_transfer_sizes): Return if
        SIZE= is not constant or source-size cannot be determined.

2012-06-17  Tobias Burnus  <burnus@net-b.de>

        PR fortran/53691
        PR fortran/53685
        * gfortran.dg/transfer_check_3.f90: New.


Added:
    trunk/gcc/testsuite/gfortran.dg/transfer_check_3.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/check.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2012-06-17 19:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 14:35 [Bug fortran/53685] New: " ajmay81 at googlemail dot com
2012-06-15 16:18 ` [Bug fortran/53685] " burnus at gcc dot gnu.org
2012-06-15 17:02 ` burnus at gcc dot gnu.org
2012-06-16 10:51 ` burnus at gcc dot gnu.org
2012-06-17 19:31 ` burnus at gcc dot gnu.org [this message]
2012-06-22 10:28 ` burnus at gcc dot gnu.org
2012-09-24 13:58 ` ajmay81 at googlemail dot com
2012-11-29 10:52 ` kloedej at knmi dot nl
2013-04-22 19:23 ` janus at gcc dot gnu.org
2013-04-26 22:50 ` janus 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-53685-4-o3gMQtX2u3@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).