Date: Wed, 8 May 2024 12:38:55 +0300 From: Jussi Korkala <jussi.korkala@icloud.com> To: bugzilla-noreply@freebsd.org Cc: threads@freebsd.org Subject: Re: [Bug 278703] Forking on 13.3 restricting to same CPU core Message-ID: <5D1B30DC-809D-405B-AB09-3537EAEC2A5D@icloud.com> In-Reply-To: <62CA3F84-2D56-427D-B760-A70CAAECB269@icloud.com> References: <62CA3F84-2D56-427D-B760-A70CAAECB269@icloud.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Whatever you do: please do not let Vixie near a console. Best regards, Jussi Korkala > On 8. May 2024, at 12.38, Jussi Korkala <jussi.korkala@icloud.com> wrote: >=20 > =EF=BB=BF > I think we may be in full on entropy/cut by thousand knives mode here. >=20 > I think the correct large scale aim is to increase negentropy. >=20 > Best regards, > Jussi Korkala >=20 >> On 7. May 2024, at 22.40, bugzilla-noreply@freebsd.org wrote: >>=20 >> =EF=BB=BFhttps://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278703 >>=20 >> --- Comment #8 from cbl@cbl.us --- >> (In reply to Alan Somers from comment #7) >> I tested 14.0 and 13.3 base LLVM versions and both are impacted. Have not= >> tested stable ye. I also compiled llvm-devel, which is v19.x, and it is a= lso >> impacted. Safe to assume all versions after v16.x are impacted based on m= y >> testing. I'd love to see the PR make it in 14.1 and the PR pushed to the= >> appropriate ports as patches for llvm16/llvm17/llvm18, etc until it makes= it >> into a newer llvm 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?5D1B30DC-809D-405B-AB09-3537EAEC2A5D>