On Mon, Aug 20, 2012 at 11:22:29AM -0700, Romain Pokrzywka wrote:
> On Sunday, August 19, 2012 11:51:05 AM Peter =?ISO-8859-1?Q?K=FCmmel?= wrote:
Hi,
adding my two cents here as well. There is and should be nothing special
about cross-compiling. With sane systems the only difference between nativ
On quarta-feira, 22 de agosto de 2012 21.15.33, marius.storm-ol...@nokia.com
wrote:
> If we should "keep it", we first need to see it I couldn't find it in
> your changes list?
I was cleaning up my changes. I also needed to disentangle from the 3-argument
testAndSet extension (5.1 feature, see [1
On 8/22/12 7:58 PM, "ext Thiago Macieira"
wrote:
>With adaptive locking:
>RESULT : tst_QMutex::contendedQMutex():"no msleep, 2 mutexes":
> 1,961,622.638 CPU ticks per iteration
> 5561.854224 task-clock#3.781 CPUs utilized
>
>17,706,600,180 cycles
On terça-feira, 21 de agosto de 2012 22.36.38, Thiago Macieira wrote:
> RESULT : tst_QMutex::contendedQMutex():"no msleep, 1 mutex":
> 4,087,893.432 CPU ticks per iteration
> 11037.507260 task-clock#2.699 CPUs
> utilized
> 33,483,481,790 cycles#
On quarta-feira, 22 de agosto de 2012 10.20.24, Thiago Macieira wrote:
> b) the locking and unlocking itself
> pthread QMutex
> locking pthread_mutex_lock pthread_mutex_lock
>
On quarta-feira, 22 de agosto de 2012 16.01.34, Thiago Macieira wrote:
> On quarta-feira, 22 de agosto de 2012 13.21.03, bradley.hug...@nokia.com
>
> wrote:
> > Wow… do you get the same results with Qt 4? I did quite a bit to optimize
> > contention performance in Qt 4. I do know that mutex content
On quarta-feira, 22 de agosto de 2012 13.21.03, bradley.hug...@nokia.com
wrote:
> Wow… do you get the same results with Qt 4? I did quite a bit to optimize
> contention performance in Qt 4. I do know that mutex contention performance
> has regressed in Qt 5 on the Mac, I wasn't sure about on Linux,
On Aug 21, 2012, at 10:36 PM, ext Thiago Macieira wrote:
> Hello
>
> I've just done some benchmarking of QMutex on Linux, using the pthread
> implementation instead of the futex one.
>
> Conclusions first:
>
> QMutex is optimised for uncontended case. It does that by keeping the d
> pointer
I had that problem too. It was looking for qhelpgenerator in the wrong
place - in qtbase/bin instead of my installed QT5 directory, where the
executable was. I ended up having to do 1 of 2 things to work around
this.
1. re-run installed qmake in the qtdocs directory
2. copy the qhelpgenerator
On quarta-feira, 22 de agosto de 2012 07.00.05, lars.kn...@nokia.com wrote:
> > When contention happens a lot, the performance is awful. I've measured
> > anything from 100% slower to over 1000%.
>
> Uhhh… is there a reason why it's that much slower than the pthread mutex? A
> factor of 2 to 10 slo
On Aug 22, 2012, at 9:16 AM, ext Äijälä Johanna
wrote:
> Hi Casper,
>
> I'm still unable to create the docs, I checked that I have latest sources
> from git, both https://codereview.qt-project.org/#change,33187 and
> https://codereview.qt-project.org/#change,32986 are included.
>
> This is
Hi Casper,
I'm still unable to create the docs, I checked that I have latest sources from
git, both https://codereview.qt-project.org/#change,33187 and
https://codereview.qt-project.org/#change,32986 are included.
This is what I'm getting:
../src/zh_CN/getting-started/how-to-learn-qt.qdoc:28:
On Aug 21, 2012, at 10:36 PM, ext Thiago Macieira
wrote:
> Hello
>
> I've just done some benchmarking of QMutex on Linux, using the pthread
> implementation instead of the futex one.
>
> Conclusions first:
>
> QMutex is optimised for uncontended case. It does that by keeping the d
> pointer
13 matches
Mail list logo
