public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dank at kegel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/11609] New: testcase gcc.dg/cleanup-5.c fails to link, undefined reference to `__gcc_personality_sj0'
Date: Sun, 20 Jul 2003 21:21:00 -0000	[thread overview]
Message-ID: <20030720212146.11609.dank@kegel.com> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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

           Summary: testcase gcc.dg/cleanup-5.c fails to link, undefined
                    reference to `__gcc_personality_sj0'
           Product: gcc
           Version: 3.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dank at kegel dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: sh4-unknown-linux-gnu

I'm building x86->sh4, x86->ppc cross-compilers using http://kegel.com/crosstool
When I build gcc-ss-3_3-20030714 targeting sh4, the test fails with

FAIL: gcc.dg/cleanup-5.c (test for excess errors)
Excess errors:
: undefined reference to `__gcc_personality_sj0'
WARNING: gcc.dg/cleanup-5.c compilation failed to produce executable

Oddly, targeting ppc doesn't fail.

cf. http://gcc.gnu.org/ml/gcc/2003-07/msg00008.html
Haven't tried that patch yet, I don't understand the issues enough to know if it
makes sense.


             reply	other threads:[~2003-07-20 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 21:21 dank at kegel dot com [this message]
2003-07-20 21:25 ` [Bug target/11609] " pinskia at physics dot uc dot edu
2003-07-24 15:35 ` pinskia at physics dot uc dot edu

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=20030720212146.11609.dank@kegel.com \
    --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).