public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Bader at lrz dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/114188] New: Overloading assignment does not invalidate intrinsic assignment
Date: Fri, 01 Mar 2024 09:40:09 +0000 [thread overview]
Message-ID: <bug-114188-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114188
Bug ID: 114188
Summary: Overloading assignment does not invalidate intrinsic
assignment
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: Bader at lrz dot de
Target Milestone: ---
Created attachment 57583
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57583&action=edit
test case for invalid use of assignment overloading
The attached reproducer overloads the assignment operator with a version that
requires the left hand side to be a pointer.
The overload conforms to the requirements for defining the assignment according
to 10.2.1.4 of the Fortran standard. Therefore, the intrinsic assignment should
become unavailable (last sentence of 10.2.1.1).
However, gfortran accepts invocations that use nonpointer arguments.
(NAG Fortran, Intel Fortran and NVidia Fortran issue appropriate error
messages).
next reply other threads:[~2024-03-01 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 9:40 Bader at lrz dot de [this message]
2024-03-01 17:28 ` [Bug fortran/114188] " kargl at gcc dot gnu.org
2024-03-01 18:00 ` Bader at lrz dot de
2024-03-01 19:11 ` kargl at gcc dot gnu.org
2024-03-01 20:25 ` anlauf 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-114188-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).