From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F29273858D33; Wed, 16 Aug 2023 14:38:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F29273858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1692196712; bh=wmAteHt1IsuBQRf/m17/zX7WN5qy0NbM2cq3xIv7rxk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gXyEFhWP41WTHzSvdMy8SuRG+9pqgXQ3UNqTVb63O6WdPUz9TNalWcXAmrIPFCNfo hsaBHJjr6kWoKF2aH7UVfxPyhzLaCLXHCKoAB0ODI39AUamDmoY6tKu0Y2kGf8suum 1K3yECA+t7hmt3he+0ClogEh1K+cGaWiO3Qdcv9E= From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/111024] libgomp: FAILs with oldish libnuma/libmemkind Date: Wed, 16 Aug 2023 14:38:32 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgomp X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: openmp, testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: attachments.created 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=3D111024 --- Comment #1 from Tobias Burnus --- Created attachment 55742 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D55742&action=3Dedit libgomp/allocator.c's gomp_init_libnuma - call numa_available() Given that (lib)memkind uses jemalloc - on Bionic in version 3.6.0, it could also be an error on that side. In libmemkind, the arena stuff seems to be rather unrelated to libnuma - an= d at least in the linked version, the call to numa_available() comes after the failing line. ("numa_available" must be called (and return !=3D -1) before = using any numa function. Thus, it seems to be unrelated to libnuma - and, hence, us calling it. Except: Well, a call to numa_available() is missing. It is worthwhile to ch= eck whether the attached patch fixes the issue - and even if not, it probably should be applied nonetheless.=