The new tests fail on darwin:
/opt/gcc/work/gcc/testsuite/gcc.target/i386/nop-mcount.c:1:0: error:
-mnop-mcount is not implemented for -fPIC
and gcc.target/i386/record-mcount.c fails because mcount_loc is not found in
the assembly.
TIA
Dominique
On Sat, Sep 27, 2014 at 01:21:29PM +0200, Dominique Dhumieres wrote:
The new tests fail on darwin:
/opt/gcc/work/gcc/testsuite/gcc.target/i386/nop-mcount.c:1:0: error:
-mnop-mcount is not implemented for -fPIC
and gcc.target/i386/record-mcount.c fails because mcount_loc is not found in
Le 27 sept. 2014 à 18:45, Dominique d'Humières domi...@lps.ens.fr a écrit :
I think the patch for gcc.target/i386/nop-mcount.c should be
--- ../_clean/gcc/testsuite/gcc.target/i386/nop-mcount.c 2014-09-26
23:29:45.0 +0200
+++ gcc/testsuite/gcc.target/i386/nop-mcount.c
On Sat, Sep 27, 2014 at 06:45:21PM +0200, Dominique d'Humières wrote:
I think the patch for gcc.target/i386/nop-mcount.c should be
True. Thanks.
-Andi
On 09/01/14 21:24, Andi Kleen wrote:
Having a nop area at the beginning of each function can be also
also useful for other things. For example it can be used to patch
functions at runtime to point to different functions, to do
binary updates without restarting the program (like ksplice or
Andi Kleen a...@firstfloor.org writes:
Ping!
From: Andi Kleen a...@linux.intel.com
The Linux kernel dynamically patches in __fentry__ calls in and
out at runtime. This allows using function tracing for debugging
in production kernels without (significant) performance penalty.
For this it
From: Andi Kleen a...@linux.intel.com
The Linux kernel dynamically patches in __fentry__ calls in and
out at runtime. This allows using function tracing for debugging
in production kernels without (significant) performance penalty.
For this it needs a table pointing to each __fentry__ call.
The
