Hi Zhigang,
Hmm. I am basically using the same or very similar sources as you.
All the sources are from checkouts from the various CVS repositories on
8 Sept 2005. The versions are binutils v2.16.91, gcc v4.1.0, and newlib
v1.13.0. I also configured my toolchain in the same way as you,
although I did not bother to install it. I just ran the test using the
built toolchain.
If the problem is still exist, I have to give
up the gcc-4.0.1 with binutils-2.16.In my enviorments , gcc 3.4.4 with
binutils-2.16.1 works very well.
Ah - well now this is very interesting! So keeping the same version of
binutils but reverting back to an older version of gcc solves the
problem, yes ? This does tend to imply that the problem might be a gcc
bug not a binutils bug. I also note that I am using gcc version 4.1.0
sources whereas you are using gcc versions 4.0.1 sources, so maybe this
is a gcc bug which has been fixed in the latest gcc sources...
Cheers
Nick
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils
