Displaying 5 results from an estimated 5 matches for "memsan".
Did you mean:
memscan
2013 Jan 03
0
[LLVMdev] Build Failure
...;
> Really, we're going to ignore errors because we can't afford one store
> in initialization code?
Essentially we don't want to pessimize code just because of a bad warning.
The other point Chandler was making, though, was that this sort of fix
means that other tools (Valgrind/MemSan) won't catch a broader class
of errors because we will have silenced them too.
>
>> The real problem with this specific warning is that gcc doesn't
>> properly track that a variable is used only under the same conditions
>> in which it is set.
>
> That is not alw...
2013 Jan 03
2
[LLVMdev] Build Failure
David Blaikie <dblaikie at gmail.com> writes:
> The other point Chandler was making, though, was that this sort of fix
> means that other tools (Valgrind/MemSan) won't catch a broader class
> of errors because we will have silenced them too.
Does buildbot do a valgrind build with the same frequency as any other
build? If so, then either we should fix the warnings or we should
disable them in the Makefile.
> Except it isn't. We can ignore t...
2013 Jan 03
3
[LLVMdev] Build Failure
"Caldarale, Charles R" <Chuck.Caldarale at unisys.com> writes:
>> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
>> On Behalf Of greened at obbligato.org
>> Subject: Re: [LLVMdev] Build Failure
>
>> It seems a better option than simply ignoring warnings and then missing
>> a real bug in the haystack of warning
2013 Jan 03
1
[LLVMdev] Build Failure
Krzysztof Parzyszek <kparzysz at codeaurora.org> writes:
>> I'm curious about this statement. Can you give an example? I've
>> committed fixes to lots of -Wuninitialized warnings in my tree. It's
>> all just initializing local variables, which shouldn't result in extra
>> stores.
>
> The logic of the program may be such that the actual store
2013 Jan 03
0
[LLVMdev] Build Failure
On Thu, Jan 3, 2013 at 10:52 AM, <dag at cray.com> wrote:
> David Blaikie <dblaikie at gmail.com> writes:
>
>> The other point Chandler was making, though, was that this sort of fix
>> means that other tools (Valgrind/MemSan) won't catch a broader class
>> of errors because we will have silenced them too.
>
> Does buildbot do a valgrind build with the same frequency as any other
> build? If so, then either we should fix the warnings or we should
> disable them in the Makefile.
>
>> Excep...