From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3B6843858403; Sun, 29 Aug 2021 14:55:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3B6843858403 From: "bqq3z3afgj at bcco4 dot anonbox.net" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/101996] libatomic: RISC-V 64: Infinite recursion in __atomic_compare_exchange_1 Date: Sun, 29 Aug 2021 14:55:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 10.3.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bqq3z3afgj at bcco4 dot anonbox.net 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2021 14:55:09 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D101996 Alpine User changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #7 from Alpine User --- Sorry for not updating this. Yes, this is indeed a bug caused by the fact t= hat Alpine's RISC-V GCC links against libatomic by default. See https://gitlab.alpinelinux.org/alpine/aports/-/issues/12948 for the downstr= eam discussion. What seems to help is running the libatomic configure script as `gcc_no_link=3Dyes ./configure`. I think this bug report can be closed in t= he meantime as this is not an upstream GCC bug.=