https://bugs.kde.org/show_bug.cgi?id=358697
--- Comment #3 from Matthias Schwarzott ---
e.g. QT has a macro like this:
#define Q_UNUSED(x) (void)x;
To be used inside functions:
Q_UNUSED(format)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358697
--- Comment #2 from Matthias Schwarzott ---
The simplest solution could be to use "(void)format" and protect this with an
ifdef checking that we are not running under the problematic static code
checker.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=358697
--- Comment #1 from Matthias Schwarzott ---
Created attachment 96891
--> https://bugs.kde.org/attachment.cgi?id=96891&action=edit
valgrind-improve-unused-parameter-on-r15763.patch
This patch implements the __attribute__ usage.
But I am not sure about
https://bugs.kde.org/show_bug.cgi?id=358697
Bug ID: 358697
Summary: valgrind.h: Some code remains even when defining
NVALGRIND
Product: valgrind
Version: 3.12 SVN
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=356817
--- Comment #1 from Matthias Schwarzott ---
Created attachment 96139
--> https://bugs.kde.org/attachment.cgi?id=96139&action=edit
valgrind-h-fix-MSVC-warning-v1
This patch fixes the issue.
But it looks a bit complicated.
It defines two different vers
https://bugs.kde.org/show_bug.cgi?id=356817
Bug ID: 356817
Summary: valgrind.h triggers compiler errors on MSVC when
defining NVALGRIND
Product: valgrind
Version: unspecified
Platform: Compiled Sources
OS: M
https://bugs.kde.org/show_bug.cgi?id=191069
--- Comment #9 from Matthias Schwarzott ---
can this be commited?
--
You are receiving this mail because:
You are watching all bug changes.
