public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54874] [OOP] polymorphic allocation with SOURCE Date: Wed, 10 Oct 2012 11:49:00 -0000 [thread overview] Message-ID: <bug-54874-4-CcaXVuMYNz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54874-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54874 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #15 from janus at gcc dot gnu.org 2012-10-10 11:49:02 UTC --- (In reply to comment #14) > > Salvatore, I would say we can close this PR (as a duplicate of PR54784), > > Fine with me. Alright, doing so. > I presume it should make its way into 4.7.3, right? Since 4.7.2 has only recently been released and we have a draft patch already, I am pretty sure it will. *** This bug has been marked as a duplicate of bug 54784 ***
prev parent reply other threads:[~2012-10-10 11:49 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-09 9:58 [Bug fortran/54874] New: OOP: " sfilippone at uniroma2 dot it 2012-10-09 10:02 ` [Bug fortran/54874] " sfilippone at uniroma2 dot it 2012-10-09 10:37 ` sfilippone at uniroma2 dot it 2012-10-09 10:48 ` dominiq at lps dot ens.fr 2012-10-09 11:03 ` sfilippone at uniroma2 dot it 2012-10-09 14:43 ` [Bug fortran/54874] [OOP] " janus at gcc dot gnu.org 2012-10-09 14:46 ` sfilippone at uniroma2 dot it 2012-10-09 14:47 ` janus at gcc dot gnu.org 2012-10-09 16:02 ` sfilippone at uniroma2 dot it 2012-10-09 16:15 ` janus at gcc dot gnu.org 2012-10-09 17:13 ` janus at gcc dot gnu.org 2012-10-09 19:42 ` janus at gcc dot gnu.org 2012-10-09 22:11 ` janus at gcc dot gnu.org 2012-10-10 10:29 ` janus at gcc dot gnu.org 2012-10-10 11:37 ` sfilippone at uniroma2 dot it 2012-10-10 11:49 ` janus at gcc dot gnu.org [this message]
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-54874-4-CcaXVuMYNz@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).