public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alexandre.poux at coria dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/114012] New: overloaded unary operator called twice Date: Tue, 20 Feb 2024 14:14:11 +0000 [thread overview] Message-ID: <bug-114012-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114012 Bug ID: 114012 Summary: overloaded unary operator called twice Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: alexandre.poux at coria dot fr Target Milestone: --- Created attachment 57470 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57470&action=edit a program triggering the duplicate call on unary operator In the attached code, I overloaded assignment (assign) and the unary operator '-' (neg) for a custom class The assign subroutine receive a polymorphic argument and the function neg returns a polymorphic result. When a simple `i = -i` is supposed to call `neg` and the `assign`, it surprisingly call `neg` twice and then `assign`. Both time `neg` is called with the correct argument (the old value of `i`) so the result is good anyway. As far as I know, `neg` and `assign` are supposed to be pure (which they are not, due to the print) so this should only induce a performance hit. I've observed this on an up to date Arch linux with core/gcc-fortran 13.2.1-5 and extra/gcc12-fortran 12.3.0-3.
next reply other threads:[~2024-02-20 14:14 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-20 14:14 alexandre.poux at coria dot fr [this message] 2024-02-20 20:32 ` [Bug fortran/114012] " anlauf at gcc dot gnu.org 2024-02-25 19:44 ` anlauf at gcc dot gnu.org 2024-02-25 20:36 ` anlauf at gcc dot gnu.org 2024-02-26 17:50 ` cvs-commit at gcc dot gnu.org 2024-02-27 9:42 ` alexandre.poux at coria dot fr 2024-03-06 21:03 ` cvs-commit at gcc dot gnu.org 2024-03-06 21:06 ` 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-114012-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: 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).