public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gronki at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46897] [OOP] type-bound defined ASSIGNMENT(=) not used for derived type component in intrinsic assign
Date: Wed, 03 Feb 2021 21:22:59 +0000 [thread overview]
Message-ID: <bug-46897-4-1bCRSq8vO2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46897-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46897
Dominik Gronkiewicz <gronki at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gronki at gmail dot com
--- Comment #14 from Dominik Gronkiewicz <gronki at gmail dot com> ---
Still affected by this bug in 10.2.1. ifort, in contrast, calls the defined
assignment, which is consistent with the cited paragraph of the standard (point
13 in 10.2.1.3 of F2018 standard draft):
I wanted to file a new bug but found this one so just bumping. :)
Dominik
next prev parent reply other threads:[~2021-02-03 21:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 22:20 [Bug fortran/46897] New: [OOP] Polymorphic type - defined ASSIGNMENT(=) not used burnus at gcc dot gnu.org
2010-12-12 22:15 ` [Bug fortran/46897] " janus at gcc dot gnu.org
2010-12-12 22:26 ` [Bug fortran/46897] defined ASSIGNMENT(=) not used for derived type component janus at gcc dot gnu.org
2010-12-13 7:37 ` burnus at gcc dot gnu.org
2010-12-13 9:08 ` janus at gcc dot gnu.org
2010-12-13 9:28 ` [Bug fortran/46897] [OOP] type-bound defined ASSIGNMENT(=) not used for derived type component in intrinsic assign janus at gcc dot gnu.org
2010-12-13 15:17 ` damian at rouson dot net
2010-12-13 16:37 ` burnus at gcc dot gnu.org
2012-08-11 13:18 ` pault at gcc dot gnu.org
2012-12-01 8:01 ` pault at gcc dot gnu.org
2012-12-03 10:02 ` burnus at gcc dot gnu.org
2013-05-22 9:19 ` burnus at gcc dot gnu.org
2013-05-22 9:22 ` burnus at gcc dot gnu.org
2013-09-15 14:19 ` burnus at gcc dot gnu.org
2021-02-03 21:22 ` gronki at gmail dot com [this message]
2022-05-25 13:08 ` trnka at scm 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-46897-4-1bCRSq8vO2@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).