| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
we should include qt_windows.h and not windows.h because we have to
define WINVER to 0x500.
|
| |
|
|
|
|
|
| |
Letting qdoc output it automatically produces the wrong header
file name.
Task-number: 217268 210171 220664
|
| |
|
|
|
|
|
| |
omissions when qdoc is used in certain Windows environments.
Task-number: 256415
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(ThreadEngineBarrier was implemented in the header as ThreadEngineSemaphore
in Qt 4.4 and Qt 4.5, and exported for a brief time in the Qt master branch. )
Unfortunately the inline call to acquire means that applications compiled
with Qt 4.4. and Qt 4.5 will contain a copy of the old implementation.
This is BC as long as the memory layout of the ThreadEngineBarrier class
stays the same, which means that we keep the QMutex member variable.
The old version of acquire will no longer be thread-safe since the new
version doesn't lock the mutex, but this is fortunately not a problem;
the only place it's called is in startAsynchronously() before the worker
threads are started.
|
| |
|
|
|
|
|
|
| |
The ThreadEngine template uses functions from ThreadEngineBarrier,
so ThreadEngineBarrier must be exported to other libraries/programs
that instantiate the template.
Reviewed-by: trustme
|
| |
|
|
| |
Also move the implementation to the .cpp file.
|
| |
|
|
|
| |
Reduce lock contention QtConcurrent by swiching the ThreadEngineSemaphore
class over to a QAtomic-based implementation.
|
| |
|
|
|
|
| |
Reduce lock contention:
- Skip locking in the accessor functions (where we can)
- exit early in tryStart (before locking the mutex) when the threadpool is running at max capacity.
|
| |\ |
|
| | |
| |
| |
| | |
Reviewed-by: Trust Me
|
| |/
|
|
| |
...hopefully
|
| |
|
|
|
|
| |
foo == QString() should be foo.isNull(). Fixes 7 warnings in the Norwegian Breakfast Network
Reviewed-by: Samuel
|
| |
|
|
|
|
|
|
|
| |
The held results were not cleared by QFutureInterface::operator=(QFutureInterface)
Add call to resultStore().clear(), similar to the destructor.
This needs to be done in the header since we know the template type here.
Task-number: 252208
Reviewed-by: brad
|
| |
|
|
|
|
|
|
| |
This results in a syscall and is very slow. Make the call once and cache
the value.
Task-number: 244718
Reviewed-by: TrustMe
|
| |
|
