Skip to content
GitLab
Select Git revision
  1. 01 Oct, 2014 - 1 commit
  3. 30 Sep, 2014 - 1 commit
  5. 29 Sep, 2014 - 1 commit
  7. 26 Sep, 2014 - 1 commit
  9. 22 Sep, 2014 - 2 commits
  11. 20 Sep, 2014 - 1 commit
    • Morten Johan Sørvig's avatar
      Don't disable C++11 on OS X and iOS · f1d879f4
      Morten Johan Sørvig authored 
      
On OS X and iOS, enabling C++11 has the side effect of switching
the standard library from libstdc++ to libc++. Qt 5.2 enables
C++11 by default, which leads to a Qt build that uses both
standard libraries. This is something we would like to avoid.
As with clang it is possible to build webkit also with C++11
instead of forcing the use of libc++ also without C++11
we simply build with C++11 on OS X and iOS.

Change-Id: I0ad8fb550ef79ac37ac97a75799ac38aa19d39d4
Reviewed-by: default avatarJake Petroules <jake.petroules@petroules.com>
      f1d879f4
  13. 18 Sep, 2014 - 1 commit
  15. 17 Sep, 2014 - 3 commits
  17. 16 Sep, 2014 - 1 commit
  19. 02 Sep, 2014 - 1 commit
  21. 29 Aug, 2014 - 1 commit
  23. 24 Aug, 2014 - 1 commit
  25. 29 Jul, 2014 - 1 commit
  27. 08 Jul, 2014 - 1 commit
  29. 07 Jul, 2014 - 1 commit
  31. 03 Jul, 2014 - 1 commit
    • Thiago Macieira's avatar
      Work around ICC optimizer bug hoisting conditions out of the loop · 11ca3481
      Thiago Macieira authored 
      
In the first iteration of the loop, span->objects is not null, but
becomes null and therefore the entry is removed from the list. When the
list is empty, the list header (nonempty_) has next == prev == self and
objects is null. So in the second iteration, DLL_IsEmpty should return
true.

Analysis of the assembly output indicates that the function DLL_IsEmpty
(DLL = "doubly linked list") was hoisted out of the loop and its
condition was never checked again.

Affects: 14.0.3 on Linux, 15 on OS X (EDG and Clang) and Linux
Does not affect: 14.0.3 on Windows

Intel issue ID: 6000056746
Change-Id: I4439f441d5206a39391b9181baf42160d37bd2f1
Reviewed-by: default avatarSimon Hausmann <simon.hausmann@digia.com>
      v5.3.2
      11ca3481
  33. 26 Jun, 2014 - 1 commit
  35. 21 Jun, 2014 - 1 commit
    • Andy Shaw's avatar
      Fix crash when creating a QScriptEngine in a native thread · 71f6dee8
      Andy Shaw authored 
      This is technicially a cherry-pick of
4e73732d3e72ea59d39ec5a5c01c2e76bbff7dc1 from 4.8. Somehow this change did
not end up in Qt 5. The details below is a copy paste from the original
change.

The change in http://trac.webkit.org/changeset/48412/

 introduced a fix
to avoid leaking thread specific data by ensuring get() on ThreadSpecific
works even during the thread destruction phase. The fix worked by setting
the local data again.

However as we can see in the backtrace from QTBUG-22926, the local data
should not be set unconditionally, otherwise our destroy function will be
called recursively when the local data is still set.

Task-number: QTBUG-22926
Change-Id: If59d7e92998b9f1da98c05b94e7b6c725ada4a75
Reviewed-by: default avatarSimon Hausmann <simon.hausmann@digia.com>
      71f6dee8
  37. 17 Jun, 2014 - 1 commit
  39. 02 Jun, 2014 - 2 commits
  41. 24 Apr, 2014 - 1 commit
  43. 17 Apr, 2014 - 1 commit
  45. 24 Mar, 2014 - 1 commit
  47. 11 Mar, 2014 - 2 commits
  49. 04 Mar, 2014 - 3 commits
  51. 27 Feb, 2014 - 1 commit
  53. 24 Feb, 2014 - 1 commit
  55. 20 Feb, 2014 - 2 commits
  57. 07 Feb, 2014 - 1 commit
  59. 05 Feb, 2014 - 3 commits