From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DD0B83858C50; Sun, 30 Apr 2023 02:55:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DD0B83858C50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1682823309; bh=JSgrS9JdpxBRoDILwigQujrsdmRwC4Au2aZwqYS64Sw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ethHrKfBzSEi/pEglLfLiTgNw4rNfhmEva1bfS1oDrckwLgqCcv64WnFArJIXOT8k 9f+cZsYULhmbIZ89QHn4ycRwqOWUNuhe7c1+NQpjeaFKQlqlJ1G4rkLMkhOri2XilQ 8uc+H62e+1DV7eexI5DajzyVZ2eWKXh7x9YsFyJA= From: "adelson.oliveira at gmail dot com" 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: Sun, 30 Apr 2023 02:55:08 +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: adelson.oliveira at gmail dot com 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 #13 from Adelson Oliveira -= -- Thanks, anlauf Em s=C3=A1b., 29 de abr. de 2023 =C3=A0s 16:00, anlauf at gcc dot gnu.org < gcc-bugzilla@gcc.gnu.org> escreveu: > 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 > it? > > 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 m= ay > take some time distros pick up the fixed gcc versions. > > For the time being, you can still use .MULT. etc. as a portable workaroun= d. > > -- > You are receiving this mail because: > You reported the bug.=