From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 56F4338582B6; Fri, 2 Feb 2024 19:31:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 56F4338582B6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706902281; bh=+z1ji93as66qC56Kt9WDEndAG2Nd2Y66CIVAMYxDMM8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=f7uAmVGioW94cOsPjC7pTaNM6CiYkT0IoLjM9IfTkyStJ1DZ6NfDU1CzuMo/Jc5Ek xg9dCgFH+5jq9mw4q53KGYLpXsRo1TKXndDXlmC+Lxy9jjyjofi87oIA2MFF9rSv5M 4GV3V12C81hUILfNcOXcMLfVUpfI1JlH9IIdpdCA= From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113721] [14 Regression][OpenMP][nvptx] cuCtxSynchronize fail when calling 'free' in the target regsion Date: Fri, 02 Feb 2024 19:31:20 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: openmp, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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: resolution 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=3D113721 Tobias Burnus changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Tobias Burnus --- Hmm, while I did see it on two systems, bisecting failed (always passing) a= nd now it passes with both the quicker build and full build. I did not complete the bisecting as I did not see interesting commits in between, hence, I cannot rule out that there was an in-between issue very recently. Nor do I rule out some odd build issue. Oddly, I had the very same issue on two system. Anyway, close as WORKSFORME.=