public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fmartinez at gmv dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52010] New: Intrinsic assignment involving CLASS/TYPE
Date: Thu, 26 Jan 2012 15:55:00 -0000	[thread overview]
Message-ID: <bug-52010-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52010
           Summary: Intrinsic assignment involving CLASS/TYPE
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: fmartinez@gmv.com


The attached examle generates a compiler error about not being able to convert
from CLASS to TYPE being the object of the same declared type.

Reported bug 41719 addresses partially this issue although looking at the
standard (7.4.1) I cannot really see that this assignment is incorrect.
The Intel compiler does not complain about this even with the stardard 2003
flags activated.


             reply	other threads:[~2012-01-26 15:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 15:55 fmartinez at gmv dot com [this message]
2012-01-26 18:40 ` [Bug fortran/52010] " dominiq at lps dot ens.fr
2012-01-26 18:42 ` fmartinez at gmv dot com
2012-01-27 17:07 ` [Bug fortran/52010] [OOP] Intrinsic assignment of a CLASS to a TYPE burnus at gcc dot gnu.org
2012-01-28 19:09 ` dominiq at lps dot ens.fr
2012-01-28 23:38 ` fmartinez at gmv dot com
2012-01-28 23:40 ` fmartinez at gmv dot com
2014-12-29  3:46 ` pault at gcc dot gnu.org
2014-12-30  3:12 ` pault at gcc dot gnu.org
2015-10-18 20:54 ` dominiq at lps dot ens.fr
2015-10-19  4:40 ` paul.richard.thomas at gmail dot com

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-52010-4@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).