From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5A7963856261; Wed, 17 May 2023 20:57:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5A7963856261 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684357037; bh=DutfPzVFnlYOwpLH42Bh+T+M8ymTkj720U2+npBBhwY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZAANDEJAhTj+Fxpv8n3yZCCrULDZC6n8UwdR9nlUVlgroHKm9V0P+fITQcYYVfXtw UFRfuDw/LrL6FUqdHEUJ17dS+FQ4Y83+xpfKdMannvG/pZgVEi4wSnIiRE1A8jILfG KyhgIqB8m+z9svh5wLE+F+iN2TsGtk/MJxipC0t0= From: "anlauf at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/81985] several sanitizer undefined runtime errors in sanitized libgfortran Date: Wed, 17 May 2023 20:57:16 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Version: 8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gcc dot gnu.org X-Bugzilla-Status: WAITING 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: bug_status 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=3D81985 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING --- Comment #3 from anlauf at gcc dot gnu.org --- I don't see the issue here anymore as we inline expand intrinsic MVBITS since gcc-11 and do no longer generate libgfortran calls. The issue might still exist in gcc-10. Shall we close this one as fixed?=