From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DC0CF3858CDA; Mon, 8 Apr 2024 21:50:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DC0CF3858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712613044; bh=NgVhAk9ZXg9x4fGyFsZnwHnMZYh6B49zcNLtYNl/mZs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OkKqVovzfarsXUA/xWFcktWa8xPPtZwa0YruJ/hmPILDTim4opvbDJeHhlwxGeB1U 1XpzxMWuHtja2dkD+xih5LKcs0i7/aPBNN6XHMmUIBT8Tk+P3oHH3GNTHx2ui0Titt CMDwmTTQhOijxYSqeOZJjHroKNmEnNetg9HqHeZ8= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/114646] libgfortran still doesn't define GTHREAD_USE_WEAK to 0 for newer glibc Date: Mon, 08 Apr 2024 21:50:44 +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: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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 resolution 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=3D114646 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #12 from Andrew Pinski --- (In reply to Bruno Haible from comment #11) > (In reply to Andrew Pinski from comment #9) > > Dup. > >=20 > > *** This bug has been marked as a duplicate of bug 87189 *** >=20 > This makes no sense to me: > - I verified that https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87189 is > fixed; therefore it ought to be marked as RESOLVED FIXED. > - Whereas H.J. is seeing this bug here with GCC 13 and glibc 2.38. > Therefore they cannot be duplicates of each other. Yes it is all the same issue. *** This bug has been marked as a duplicate of bug 78017 ***=