public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tbm at cyrius dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38642]  New: [4.3/4.4 Regression] Code with -fPIC results in segfault on ARM (old ABI)
Date: Sat, 27 Dec 2008 16:51:00 -0000	[thread overview]
Message-ID: <bug-38642-12387@http.gcc.gnu.org/bugzilla/> (raw)

[ Forwarded from http://bugs.debian.org/487406 ]

Enrico Zini reported the following bug (with testcase) to Debian: the attached
code compiled with -fPIC results in a segfault on ARM (old ABI; not on EABI).

It works fine on other architectures or on ARM with gcc 4.2.

I verified that the bug is present in gcc 4.3 from SVN and in trunk.


-- 
           Summary: [4.3/4.4 Regression] Code with -fPIC results in segfault
                    on ARM (old ABI)
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tbm at cyrius dot com
GCC target triplet: arm-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38642


             reply	other threads:[~2008-12-27 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-27 16:51 tbm at cyrius dot com [this message]
2008-12-27 16:51 ` [Bug target/38642] " tbm at cyrius dot com
2009-01-01  5:14 ` pinskia at gcc dot gnu dot org
2009-01-03 15:31 ` rguenth at gcc dot gnu dot org
2009-01-24 10:28 ` rguenth at gcc dot gnu dot org
2009-07-10  9:45 ` [Bug target/38642] [4.3/4.4/4.5 " ramana at gcc dot gnu dot org
2009-07-11 15:23 ` mikpe at it dot uu dot se
2009-07-19 22:29 ` mikpe at it dot uu dot se
2009-08-04 12:45 ` rguenth at gcc dot gnu dot org
2010-05-22 18:28 ` [Bug target/38642] [4.3/4.4/4.5/4.6 " rguenth 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=bug-38642-12387@http.gcc.gnu.org/bugzilla/ \
    --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).