This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/26636] use of r1-r3 across __sdivsi3_4 call
- From: "rmansfield at qnx dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 May 2007 02:01:22 -0000
- Subject: [Bug target/26636] use of r1-r3 across __sdivsi3_4 call
- References: <bug-26636-11406@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from rmansfield at qnx dot com 2007-05-10 03:01 -------
Thanks for looking at the PR. Has sdivsi3_i4 has always been hidden? I still
link against some shared libraries built with 2.95.3 where __sdivsi3_i4 is not
hidden. r1-r3 are in the clobber list for 2.95.3 so I don't trip if compile
with 2.95.3
For example:
$ readelf.exe -s libm.so | grep sdivsi3_i4
23: 0000a8b4 14 FUNC GLOBAL DEFAULT 9 __sdivsi3_i4
129: 0000a8b4 14 FUNC GLOBAL DEFAULT 9 __sdivsi3_i4
If I compile my program with gcc 3.4/4.x and the 2.95.3 libm.so appears before
the libgcc.a, a plt stub gets generated, r1 ends up gettng clobbered and the
program crashes.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26636