From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0EF4D384773E; Wed, 3 Apr 2024 22:10:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0EF4D384773E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712182222; bh=owxjyXH1C+M57H0s1epuBIaHDm5KLtY+TVPA5X+rDAI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qupb2HfD7zr+9GoRAJUFEjy3uZeWPcCSaSvQd1mJ1pToH4jZcq4TyZcmX3xQTio/g DPob2UMavGvA1c/V8sFQcrA7hLsprLCJnPI/wMu9UFTGNNs0S6TA3I85H2svTSBpan gVtJ46zsO8MJeorZjIepX4KqOE+ZqzjOXoZNe6mU= From: "bunk at stusta dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/81358] libatomic not automatically linked with C11 code Date: Wed, 03 Apr 2024 22:10:19 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: driver X-Bugzilla-Version: 7.1.1 X-Bugzilla-Keywords: link-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: bunk at stusta dot de 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=3D81358 --- Comment #15 from Adrian Bunk --- (In reply to Tobias Burnus from comment #11) > RFC draft patch =E2=80=93 also to solve an offload problem with atomic an= d nvptx > libgomp: > https://gcc.gnu.org/pipermail/gcc-patches/2020-October/556297.html > See reply for what still needs to be done (esp. related to building > libraries + testsuite). Was there any reason why this was stalled? More and more packages in Debian need manual addition of libatomic on some 32bit vintage architectures (armv5/m68k/mips/powerpc/sh4) due to this, whic= h is a pain. Is the only issue that noone has addressed the comments in the reply on the mailing list, or have there also been other problems?=