Siarhei Siamashka wrote:
I'm not going to statically link with glibc, but only with libstdc++ (standard
c++ library). There are a few known tricks to make gcc link with libstdc++
statically, but dynamically with all the rest of libraries. One of them is
creating a symlink to libstdc++.a in some
Hi,
ext Siarhei Siamashka wrote:
Did you also read Intel docs? Unaligned access has some restrictions
on x86 as well. Do you have an example of some practical case where
hardware unaligned support from ARM11 would work worse than on x86?
No. Would be nice if somebody would test it.
The
Siarhei Siamashka wrote:
Hm. The toolchain might not be built with -pg support.
As to using gprof, that produces fairly unreliable results.
I'd recommend building Oprofile kernel and latest oprofile
user-space tools.
Maybe Oprofile is good, but gprof is better than nothing and does not
Hi,
ext Siarhei Siamashka wrote:
By the way, do you have any plans for upgrading toolchain? Either I'm
extremely unlucky, or current toolchain is really very buggy.
You can see the known issues from the GCC bugzilla.
There are a few bugs in C++ support which have been fixed
in gcc 3.4.6
On Wednesday 02 May 2007 18:48, Eero Tamminen wrote:
On x86 I prefer valgrind/cachegrind/callgrind/kcachegrind as
that way one can browse the source code interactively with
the profiling information. Getting to know how the source
really works is sometimes more useful than knowing the exact
On Tuesday 24 April 2007 10:56, you wrote:
By the way, do you have any plans for upgrading toolchain? Either I'm
extremely unlucky, or current toolchain is really very buggy.
You can see the known issues from the GCC bugzilla.
There are a few bugs in C++ support which have been fixed
in
