Alexe Stefan writes:
> So it's only useful for developers that already use valgrind.
Why would it be useful to anybody else? It can be useful if you suspect
you may want to use Valgrind with system packages at some point and you
don't want then to recompile, sure.
I'm not sure if I understand
So it's only useful for developers that already use valgrind.
sâm., 27 mai 2023, 17:13 Sam James a scris:
>
> Alexe Stefan writes:
>
> > In that case, is it worth it to enable USE=valgrind globally?
>
> I have, and I'd say others interested in using Valgrind should too.
>
>
>
Alexe Stefan writes:
> In that case, is it worth it to enable USE=valgrind globally?
I have, and I'd say others interested in using Valgrind should too.
signature.asc
Description: PGP signature
In that case, is it worth it to enable USE=valgrind globally?
vin., 26 mai 2023, 10:44 Sam James a scris:
>
> Sam James writes:
>
> > [[PGP Signed Part:Undecided]]
> >
> > Sam James writes:
> >
> >> Alexe Stefan writes:
> >>
> >>> Does enabling USE=valgrind impact runtime performance in any
Sam James writes:
> [[PGP Signed Part:Undecided]]
>
> Sam James writes:
>
>> Alexe Stefan writes:
>>
>>> Does enabling USE=valgrind impact runtime performance in any way?
>>
>> A very small amount because it adds a check at runtime for whether
>> the application is running under Valgrind. The
Sam James writes:
> Alexe Stefan writes:
>
>> Does enabling USE=valgrind impact runtime performance in any way?
>
> A very small amount because it adds a check at runtime for whether
> the application is running under Valgrind. The compiler may be able
> to optimise this a bit if it can
Alexe Stefan writes:
> Does enabling USE=valgrind impact runtime performance in any way?
A very small amount because it adds a check at runtime for whether
the application is running under Valgrind. The compiler may be able
to optimise this a bit if it can determine it's unlikely (if the
Does enabling USE=valgrind impact runtime performance in any way?
dum., 14 mai 2023, 19:46 Arsen Arsenović a scris:
>
> Sam James writes:
>
> > This always has the same meaning in packages - build in annotations to
> help
> > with e.g. custom memory allocators to reduce noise and improve
>
Sam James writes:
> This always has the same meaning in packages - build in annotations to help
> with e.g. custom memory allocators to reduce noise and improve Valgrind's
> accuracy.
>
> All invalid uses of this were already fixed (cases where it was used to
> control
> running the testsuite
On Sun, 2023-05-14 at 09:26 +0100, Sam James wrote:
> This always has the same meaning in packages - build in annotations to
> help
> with e.g. custom memory allocators to reduce noise and improve
> Valgrind's accuracy.
>
> All invalid uses of this were already fixed (cases where it was used
> to
This always has the same meaning in packages - build in annotations to help
with e.g. custom memory allocators to reduce noise and improve Valgrind's
accuracy.
All invalid uses of this were already fixed (cases where it was used to control
running the testsuite under Valgrind which we don't want
11 matches
Mail list logo
