Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 May 2024 12:36:39 +0300
From:      Jussi Korkala <jussi.korkala@icloud.com>
To:        bugzilla-noreply@freebsd.org
Cc:        threads@freebsd.org
Subject:   Re: [Bug 278845] OpenMP Patches to prevent locking, hanging and CPU limiting to single core.
Message-ID:  <F3A6955B-0618-466E-9BD2-5A7EBA07523D@icloud.com>
In-Reply-To: <bug-278845-13406@https.bugs.freebsd.org/bugzilla/>
References:  <bug-278845-13406@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help

Typically the single core hangs may be in deliberately obfuscated code by Vi=
xie crew we know how much those people like to waste cpu resources =C3=A1 la=
 GCC.

Best regards,
Jussi Korkala

> On 8. May 2024, at 1.49, bugzilla-noreply@freebsd.org wrote:
>=20
> =EF=BB=BFhttps://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278845
>=20
>            Bug ID: 278845
>           Summary: OpenMP Patches to prevent locking, hanging and CPU
>                    limiting to single core.
>           Product: Base System
>           Version: 14.0-STABLE
>          Hardware: Any
>                OS: Any
>            Status: New
>          Severity: Affects Only Me
>          Priority: ---
>         Component: threads
>          Assignee: threads@FreeBSD.org
>          Reporter: cbl@cbl.us
>                CC: dim@FreeBSD.org
>=20
> We worked with LLVM OpenMP development group to get a couple of PR fixes a=
dded
> to fix some big bugs we've been experiencing.
>=20
> Fix#1 - Fixes forked processes from hanging:
> https://github.com/llvm/llvm-project/pull/88539
> Original issue reported: https://github.com/llvm/llvm-project/issues/86684=

>=20
> Fix#2 - Fixes child processes to use affinity_none. Before they were limit=
ed to
> using a single cpu core for all child processes.
> https://github.com/llvm/llvm-project/pull/91391
> Original issue reported: https://github.com/llvm/llvm-project/issues/91098=

>=20
> Fix#2 is only needed in version of llvm 16.x and later.  My original issue=

> shows it's not an issue in 14.x or 15.x. Since FreeBSD 14.0 and 13.3 lever=
age
> 16.x and 17.x, this bug was triggered when we upgraded servers to either
> release.
>=20
> Hoping we can get both into 14.1 in time for it's upcoming release.
>=20
> --
> You are receiving this mail because:
> You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F3A6955B-0618-466E-9BD2-5A7EBA07523D>