https://bugs.kde.org/show_bug.cgi?id=376064
--- Comment #1 from Stephen Kelly ---
I can't reproduce this with
$ g++ --version
g++ (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying condi
https://bugs.kde.org/show_bug.cgi?id=374801
Stephen Kelly changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/ext |https://commits.kde.org/ext
https://bugs.kde.org/show_bug.cgi?id=374801
Stephen Kelly changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=374801
--- Comment #11 from Stephen Kelly ---
Damn, useEnum should use uint instead of the flags type like this:
void useEnum(int foo = 100, uint flags = EnumValueOne);
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374801
--- Comment #10 from Stephen Kelly ---
Here's an updated version of those two files:
#!/usr/bin/env python
from __future__ import print_function
import sys
from clang import cindex
from clang.cindex import Curso
https://bugs.kde.org/show_bug.cgi?id=374801
--- Comment #9 from Stephen Kelly ---
Superb, thanks for reducing it to that. Now let's see if we can get a reduced
testcase showing it is an upstream bug somehow.
Please create a file called clang-param-test.h containing
enum MyFla
https://bugs.kde.org/show_bug.cgi?id=374801
--- Comment #7 from Stephen Kelly ---
I don't understand and I can't reproduce this. We have a test in
extra-cmake-modules that works for you and has almost the same thing as this
kguiaddons header.
What libclang version do you have?
I thi
https://bugs.kde.org/show_bug.cgi?id=374801
--- Comment #5 from Stephen Kelly ---
Created attachment 103315
--> https://bugs.kde.org/attachment.cgi?id=103315&action=edit
kguiaddons debug output
Strange.
Please now add this patch to ECM, and run the build of kguiaddons and paste the
https://bugs.kde.org/show_bug.cgi?id=374801
--- Comment #3 from Stephen Kelly ---
Created attachment 103313
--> https://bugs.kde.org/attachment.cgi?id=103313&action=edit
More debug output
Please apply the attached patch to your extra-cmake-modules and run
cd build
rm -r
https://bugs.kde.org/show_bug.cgi?id=374801
--- Comment #1 from Stephen Kelly ---
Thanks for trying this.
Can you please post the
/build/kguiaddons/src/build/src/sip/PyKF5/KGuiAddons/kfontutils.sip file and
indicate line 14?
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=361691
--- Comment #12 from Stephen Kelly ---
Your benchmark is only for the case of the searched string being empty. In
other benchmarks here, the two perform the same.
That isn't a good reason for clazy to recommend something that 1) goes agains
https://bugs.kde.org/show_bug.cgi?id=361691
Stephen Kelly changed:
What|Removed |Added
Resolution|INVALID |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=361691
--- Comment #9 from Stephen Kelly ---
Upstreamed: https://bugreports.qt.io/browse/QTBUG-52617
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361691
--- Comment #7 from Stephen Kelly ---
Or a 100% difference, depending how you see it :).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361691
--- Comment #4 from Stephen Kelly ---
I also tried with larger strings. The fact that the QLatin1String overload is
slower is suspect. It could be due to the test string being very small, but
that's what I expect is the primary use-ca
https://bugs.kde.org/show_bug.cgi?id=361691
--- Comment #3 from Stephen Kelly ---
I tried to replicate your result unsuccessfully. Do you still have your
benchmark? I tried Qt 5.4.2 and some recent git branch.
#include
class StringBenchmark : public QObject
{
Q_OBJECT
public
https://bugs.kde.org/show_bug.cgi?id=361691
--- Comment #2 from Stephen Kelly ---
That sounds like a bug in QString, right?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361691
Bug ID: 361691
Summary: Suggestion to turn string into QStringLiteral instead
of QLatin1String
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=352369
Stephen Kelly changed:
What|Removed |Added
Latest Commit||http://commits.kde.org/kite
https://bugs.kde.org/show_bug.cgi?id=352369
Stephen Kelly changed:
What|Removed |Added
Assignee|kdelibs-b...@kde.org|steve...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=354883
--- Comment #13 from Stephen Kelly ---
Hi Rhys,
Ok, thanks for the response. So in terms of realistic expections, I shouldn't
expect valgrind with Qt5 to work on OSX for now.
Thanks for the update.
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=354883
--- Comment #11 from Stephen Kelly ---
(In reply to Stephen Kelly from comment #10)
> Hi am trying to run valgrind on OSX and I think I am hitting the same
> problem.
>
> I have this embarrassingly simple Qt 5 program:
>
> cat main
https://bugs.kde.org/show_bug.cgi?id=354883
Stephen Kelly changed:
What|Removed |Added
CC||steve...@gmail.com
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=359572
--- Comment #3 from Stephen Kelly ---
I guess we currently just let cmake do whatever it does by default here. What
does cmake do regarding windows here?
--
You are receiving this mail because:
You are watching all bug changes.
24 matches
Mail list logo
