Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I76075ba7fb535febe7a723ec80451eb9d61cf1ec
|
|
Change-Id: Id0e49a99f2862d6dcc05f176769fdee0643524ee
|
|
Change-Id: Iba0502c83eb32f24691a4c0645ba1434033bfbc4
Reviewed-by: Sergio Ahumada <sahumada@blackberry.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
Conflicts:
.qmake.conf
Change-Id: I10d4f9e993d23750a6e8ddc1291b79e47fc83c64
|
|
Change-Id: I211610ee4153fa1e24de085d64bd735ce3746ae0
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
|
|
Also clean up and compile the repository with exceptions
disabled again.
Change-Id: I653ae89353284b2f4ab884384f8ea6a5d100785d
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
|
|
Change-Id: I3eee67a18f24ac5b68e7cc9dc1ba256746dbbb9e
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
|
|
This allows CI to screen for warnings in src and tools code. It does
not apply to examples or tests.
This is the same as commit 7012db159bc4196444ace26991b24a31e3fba495 in
qtbase.
Change-Id: I0ea00fbd4b45156dedabfd16a3cb3e5f6170f23f
Reviewed-by: Alan Alpert <aalpert@blackberry.com>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
|
|
Older versions appear to be much more sensitive to missing
unwind tables, and as it turns out: We were compiling QtQuick (not QtQml)
with -fno-exceptions.
Since the entire module has access to the private V4 API and may therefore
be subject to exception traversal, make sure to compile the entire module
with CONFIG += exceptions.
Change-Id: If2d029879392c22af7da2f1bba94366d51518226
Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>
|
|
We need to be able to reliably generate stack back traces for JavaScript
calls, and since we use the C stack we therefore need to be able to reliably
walk the stack.
On most platforms the stack back trace generation is tied to the same
mechanism that's used to unwind the stack during exception handling,
which uses compiler generated per-function tables that allow the run-time
to unwind the stack even when no regular stack frame was created.
Unfortunately on i386 on Windows there are no unwinding tables in use (as
opposed to all other architectures Windows runs on), and therefore we have no
reliable way of generating a stack back trace if functions can omit the
generation of a stack frame. Therefore we have to disable this compiler
optimization, using -Oy- for MSVC (see http://msdn.microsoft.com/en-us/library/2kxx5t2c(v=vs.71).aspx )
and -fno-omit-frame-pointer for gcc.
Technically this change needs to be done only in places where we support
throwing or catching V4 exception as well as code that is traversed during the
unwinding. Due to the use of internal V4 api throughout the entire module,
this patch is applied to .qmake.conf.
This also fixes tst_qqmlvaluetypes
Change-Id: I21a9e5522741446de25a5d0046f7e34f741f7722
Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>
|
|
Change-Id: Iedf4bf32512c218e3ad9b89a1ad25b971b828b58
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
|
|
Change-Id: I3d794f16eb81634b9fe69d4fc9559be19cf3a998
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
|
|
Task-number: QTBUG-29838
Change-Id: I03ce9975ede5cff53e976409e2fabff1f56e1ea9
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
|
|
follow respective change in qtbase
Change-Id: I27502eb7ebea973e19ec5f7c3ec0e2338556f6e0
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
Reviewed-by: Alan Alpert (Personal) <416365416c@gmail.com>
|
|
Change-Id: Ide2e054e9b5b58976410d16ca4f76fd55e61676d
Reviewed-by: Joerg Bornemann <joerg.bornemann@nokia.com>
|