Date: Wed, 18 Oct 2023 13:04:19 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Paul Floyd <paulf2718@gmail.com> Cc: "freebsd-hackers@FreeBSD.org" <freebsd-hackers@freebsd.org> Subject: Re: Valgrind 3.22 RC1 announced Message-ID: <ZTA6Q59Y2hD9DYw1@troutmask.apl.washington.edu> In-Reply-To: <6509AC79-3080-42A8-8E34-87974C15491C@gmail.com> References: <01a7debc-bdc4-4aba-9f8d-1b78a00aac3c@gmail.com> <ZTAcWnUzVqZDzb39@troutmask.apl.washington.edu> <6509AC79-3080-42A8-8E34-87974C15491C@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 18, 2023 at 09:34:36PM +0200, Paul Floyd wrote: > > > > On 18 Oct 2023, at 19:56, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > > > > > > Is https://bugs.kde.org/show_bug.cgi?id=381819 fixed? > > If not, are there plans to include the patch attached > > to the bug report in the FreeBSD port? > > > No, that didn’t make it. I ran out of time to write a test > case, plus I don’t have anything to test it on. > > It’s likely to be one of the next things that I try to resolve. > Thanks for the info. That issues has been a thorn in my side while working on gcci/gfortran patches for a long time. I typically use the -mno-tbm option, but how to insure that is in effect everywhere is pain. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZTA6Q59Y2hD9DYw1>