From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5F2D63858C50; Sat, 29 Apr 2023 19:00:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5F2D63858C50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1682794852; bh=zhIvbsbGTfS9cplr6En2dLnovHDpU0o+3q7HEaN9NHY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=CTcbugW+s43Lpwa9/9UAP8vlTajNjkyNiB93fN0pTE3HohjFEhLRM8kkcB/RaIyQj BMn/fNtj1ttAUEf1zg8XNM5Ner8f0GOcLCD04LfenJxbMaPjiW6O4WbzqeSJfY/JrA 1GkQmM1K+RJTKIJE/iBvB1XbfpFPpMqI/p2FndDc= From: "anlauf at gcc dot 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: Sat, 29 Apr 2023 19:00:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 10.1.0 X-Bugzilla-Keywords: accepts-invalid, rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109641 --- Comment #12 from anlauf at gcc dot gnu.org --- (In reply to Adelson Oliveira from comment #11) > I'm a linux user and gfortran comes with my distro. I mean, I did not > compile gcc. > Is this patch still to be tested? Am I expected to do something to test i= t? No, this is more a proof-of-concept how to fix the issue. It is incomplete, as it does not yet handle all intrinsic binary operators (e.g. =3D=3D, /=3D= need to be handled as well). > Or I just wait until a new gfortran version is released? Once a fix is pushed, you could try to compile gcc yourself, because it may take some time distros pick up the fixed gcc versions. For the time being, you can still use .MULT. etc. as a portable workaround.=