public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vehre at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44672] [F08] ALLOCATE with SOURCE and no array-spec
Date: Wed, 29 Jul 2015 07:51:00 -0000	[thread overview]
Message-ID: <bug-44672-4-5KblmRJ1r1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44672-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44672

--- Comment #12 from vehre at gcc dot gnu.org ---
This is a bigger change to the code and we already have seen a few bugs it
caused. This means, that backporting will be a bigger effort and I don't
assume, that there will be much support on the gfortran mailing list. But you
are free to get an opinion there whether the patch will be accepted for
backporting.


  parent reply	other threads:[~2015-07-29  7:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44672-4@http.gcc.gnu.org/bugzilla/>
2013-01-08 12:34 ` [Bug fortran/44672] [F2008] " dominiq at lps dot ens.fr
2013-06-17  0:57 ` quantheory at gmail dot com
2013-07-25 12:17 ` burnus at gcc dot gnu.org
2013-12-07 14:23 ` [Bug fortran/44672] [F08] " janus at gcc dot gnu.org
2014-11-23  7:34 ` vinzent.boerner at gmx dot de
2015-03-30 17:32 ` vehre at gcc dot gnu.org
2015-03-31 10:45 ` vehre at gcc dot gnu.org
2015-05-28  7:02 ` vehre at gcc dot gnu.org
2015-06-17  8:32 ` vehre at gcc dot gnu.org
2015-07-29  7:51 ` vehre at gcc dot gnu.org [this message]
2015-09-29 12:10 ` zmi007 at gmail dot com
2015-09-29 13:02 ` vehre 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-44672-4-5KblmRJ1r1@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).