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/57596] Wrong code for allocatable deferred-length strings Date: Fri, 14 Jun 2013 07:42:00 -0000 [thread overview] Message-ID: <bug-57596-4-AMf3YXD07I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57596-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57596 --- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> --- Author: burnus Date: Fri Jun 14 07:41:42 2013 New Revision: 200084 URL: http://gcc.gnu.org/viewcvs?rev=200084&root=gcc&view=rev Log: 2013-06-14 Tobias Burnus <burnus@net-b.de> PR fortran/57596 * trans-decl.c (gfc_trans_deferred_vars): Honor OPTIONAL for nullify and deferred-strings' length variable. 2013-06-14 Tobias Burnus <burnus@net-b.de> PR fortran/57596 * gfortran.dg/deferred_type_param_9.f90: New. Added: trunk/gcc/testsuite/gfortran.dg/deferred_type_param_9.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-decl.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2013-06-14 7:42 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-12 13:54 [Bug fortran/57596] New: select type bug with optional variables? valeryweber at hotmail dot com 2013-06-12 16:22 ` [Bug fortran/57596] " burnus at gcc dot gnu.org 2013-06-13 7:23 ` [Bug fortran/57596] Wrong code for allocatable deferred-length strings burnus at gcc dot gnu.org 2013-06-13 9:14 ` burnus at gcc dot gnu.org 2013-06-14 7:42 ` burnus at gcc dot gnu.org [this message] 2013-06-14 7:43 ` 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-57596-4-AMf3YXD07I@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).