PROBLEM:
On all of my Linux x86_64 systems, when I build code instrumented for
profiling with gcc -pg, the running times reported for the code by gprof
are many times the actual runtime of the program. This problem is
specific to x86_64; the times for the same code are correct on 32-bit
x86 L
On Tue, Jun 20, 2006 at 07:29:58PM +0200, Soeren Gerlach wrote:
> I don't understand the problem at all. "-shared" means to create a shared
> library. On
> the other hand "-Bstatic" means to link a library statically into the target.
> On my
> oppinion (sorry, I'm only an application developer )
On Tue, Jun 20, 2006 at 05:03:19PM -0700, Eric Hodel wrote:
> This bug appears on the second run of a command. I may be doing
> something BFD/GDB considers sneaky. This script uses RubyInline
> which compiles and dynamically links a shared library. Each run
> removes the shared library for
--- Additional Comments From cgray at cse dot unsw dot edu dot au
2006-06-22 06:59 ---
I'm confused. You don't believe that ld doing these relocations creates a fixed
fixed address relationship between segments? Or you don't believe that this is
what the IA64 ABI is saying you can't do?
