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/52024] [OOP] GENERIC operator cannot be resolved
Date: Wed, 01 Feb 2012 19:15:00 -0000	[thread overview]
Message-ID: <bug-52024-4-zGj5yBXCux@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52024-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #11 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-02-01 19:14:54 UTC ---
FIXED on the trunk (4.7).

Thanks Dominique for updated test case.

(In reply to comment #9)
> However, I believe that test case is valid.

Actually, I now think that it invalid and correctly rejected by gfortran, cf.
http://gcc.gnu.org/ml/fortran/2012-01/msg00278.html


      parent reply	other threads:[~2012-02-01 19:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 22:16 [Bug fortran/52024] New: " fmartinez at gmv dot com
2012-01-27 22:25 ` [Bug fortran/52024] " fmartinez at gmv dot com
2012-01-28 10:22 ` burnus at gcc dot gnu.org
2012-01-28 10:51 ` burnus at gcc dot gnu.org
2012-01-28 15:12 ` burnus at gcc dot gnu.org
2012-01-28 21:01 ` dominiq at lps dot ens.fr
2012-01-31 19:14 ` burnus at gcc dot gnu.org
2012-01-31 19:58 ` burnus at gcc dot gnu.org
2012-01-31 21:08 ` burnus at gcc dot gnu.org
2012-02-01 19:06 ` burnus at gcc dot gnu.org
2012-02-01 19:15 ` burnus 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-52024-4-zGj5yBXCux@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).