public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109641] Gfortran fails to overload intrinsic operator (*) if operands are complex. It works with real ones. Date: Thu, 18 May 2023 17:01:52 +0000 [thread overview] Message-ID: <bug-109641-4-6Lopz7KKIx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109641-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109641 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Target Milestone|--- |13.2 Resolution|--- |FIXED --- Comment #18 from anlauf at gcc dot gnu.org --- Fixed on mainline for gcc-14, and backported to 13-branch. Closing. Thanks for the report!
next prev parent reply other threads:[~2023-05-18 17:01 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-27 1:41 [Bug fortran/109641] New: " adelson.oliveira at gmail dot com 2023-04-27 18:04 ` [Bug fortran/109641] " anlauf at gcc dot gnu.org 2023-04-27 19:21 ` anlauf at gcc dot gnu.org 2023-04-27 20:15 ` anlauf at gcc dot gnu.org 2023-04-27 20:54 ` anlauf at gcc dot gnu.org 2023-04-28 0:34 ` adelson.oliveira at gmail dot com 2023-04-28 1:15 ` kargl at gcc dot gnu.org 2023-04-28 1:35 ` adelson.oliveira at gmail dot com 2023-04-28 1:37 ` adelson.oliveira at gmail dot com 2023-04-28 2:21 ` sgk at troutmask dot apl.washington.edu 2023-04-28 21:07 ` anlauf at gcc dot gnu.org 2023-04-29 2:20 ` adelson.oliveira at gmail dot com 2023-04-29 19:00 ` anlauf at gcc dot gnu.org 2023-04-30 2:55 ` adelson.oliveira at gmail dot com 2023-04-30 23:19 ` adelson.oliveira at gmail dot com 2023-05-01 16:31 ` anlauf at gcc dot gnu.org 2023-05-05 19:23 ` cvs-commit at gcc dot gnu.org 2023-05-18 16:54 ` cvs-commit at gcc dot gnu.org 2023-05-18 17:01 ` anlauf at gcc dot gnu.org [this message] 2023-05-19 0:41 ` adelson.oliveira 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-109641-4-6Lopz7KKIx@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).