diff options
| author | Pedro Alves <palves@redhat.com> | 2016-04-12 17:20:04 +0100 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2016-04-12 17:20:04 +0100 |
| commit | 173981bc49c9e8fce9271cb47714952dbe2ec627 (patch) | |
| tree | 9b7d5064d89ec8c34422be04239d51ca07620b73 /gdb/cp-support.c | |
| parent | 2afc13ff80492278154c0f2156a9d32dd5ba675a (diff) | |
| download | binutils-gdb-173981bc49c9e8fce9271cb47714952dbe2ec627.tar.gz | |
Use setjmp/longjmp for TRY/CATCH instead of sigsetjmp/siglongjmp
Now that we don't ever throw GDB exceptions from signal handlers [1],
we can switch to have TRY/CATCH implemented in terms of plain
setjmp/longjmp instead of sigsetjmp/siglongjmp.
In https://sourceware.org/ml/gdb-patches/2015-02/msg00114.html, Yichun
Zhang mentions a 11%/14%+ speedup in his GDB python scripts with a
patch that did something similar to only a specific set of TRY/CATCH
calls.
[1] - https://sourceware.org/ml/gdb-patches/2016-03/msg00351.html
Tested on x86_64 Fedora 23, native and gdbserver.
gdb/ChangeLog:
2016-04-12 Pedro Alves <palves@redhat.com>
* common/common-exceptions.c (struct catcher) <buf>: Now a
'jmp_buf' instead of SIGJMP_BUF.
(exceptions_state_mc_init): Change return type to 'jmp_buf'.
(throw_exception): Use longjmp instead of SIGLONGJMP.
* common/common-exceptions.h: Include <setjmp.h> instead of
"gdb_setjmp.h".
(exceptions_state_mc_init): Change return type to 'jmp_buf'.
[GDB_XCPT == GDB_XCPT_SJMP] (TRY): Use setjmp instead of
SIGSETJMP.
* cp-support.c: Include "gdb_setjmp.h".
Diffstat (limited to 'gdb/cp-support.c')
| -rw-r--r-- | gdb/cp-support.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/cp-support.c b/gdb/cp-support.c index c7f507435f7..5662f862497 100644 --- a/gdb/cp-support.c +++ b/gdb/cp-support.c @@ -34,7 +34,7 @@ #include "cp-abi.h" #include "namespace.h" #include <signal.h> - +#include "gdb_setjmp.h" #include "safe-ctype.h" #define d_left(dc) (dc)->u.s_binary.left |