public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmansfield at qnx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/26636] use of r1-r3 across __sdivsi3_4 call
Date: Thu, 10 May 2007 02:01:00 -0000	[thread overview]
Message-ID: <20070510020122.24754.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26636-11406@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2007-05-10  2:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 18:16 [Bug target/26636] New: " rmansfield at qnx dot com
2006-03-10 18:23 ` [Bug target/26636] " rmansfield at qnx dot com
2006-03-15 16:20 ` rmansfield at qnx dot com
2007-05-09 23:05 ` kkojima at gcc dot gnu dot org
2007-05-10  2:01 ` rmansfield at qnx dot com [this message]
2007-05-10  2:19 ` kkojima at gcc dot gnu dot org
2007-05-10  3:55 ` rmansfield at qnx dot com
2007-05-10  4:25 ` kkojima at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070510020122.24754.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).