Hi Everyone,
I have an Ubuntu 9.04 system that I've installed gcc-4.5.1 on, using an in-tree
build of gmp, mpfr, mpc, and libelf.
lu...@node:~$ gcc-4.5.1 -v
Using built-in specs.
COLLECT_GCC=gcc-4.5.1
COLLECT_LTO_WRAPPER=/home/luked/local/libexec/gcc/x86_64-unknown-linux-gnu/4.5.1/lto-
Is there a way to
access stack pointer and stack size (and the direction in which the
stack is growing) on the tree level?
The explanation why I want to save the stack contents is the following:
Code:
... use stack variables
__tm_atomic { /* begin transaction */
access shared locations in he
Paolo Carlini wrote:
Luke Dalessandro wrote:
I'm making some modifications to exception handling inside of
unwind-dw2-fde.c that I'd like to use __sync_bool_compare_and_swap
for, unfortunately I can't seem to figure out how to correctly use
builtins in the context of libgcc.
I'm making some modifications to exception handling inside of unwind-dw2-fde.c
that I'd like to use __sync_bool_compare_and_swap for, unfortunately I can't
seem to figure out how to correctly use builtins in the context of libgcc.
I've tried a bunch of different things, but I consistently get t
David Edelsohn wrote:
Luke Dalessandro writes:
Luke> Thank you, this was indeed the problem. I added the needed stubbs in
Luke> gthr-single.h and it now compiles fine. Unfortunately there seems to be
Luke> something wrong with my installation of ld as linking fails with a large
Luk
David Edelsohn wrote:
Luke Dalessandro writes:
Luke> My problem is that unwind-dw2-fde.c seems to be compiled multiple times during
Luke> a gcc build, and sometimes my additions are found but other times they are
Luke> not. I am rebuilding again (AIX 5.1), and I'll post more i
We have code that fails to scale do to the object_mutex lock in
unwind-dw2-fde.c. This mutex protects two lists local to the file. The primary
list is used in "read-mostly" mode, with the secondary list used rarely when
writing needs to happen.
I am trying to change this locking scheme to use