public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rearnsha@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rslaughter@anatel.com
Subject: Re: target/4702: arm-elf-gcc  generates undefined for __gxx_personality_sj0
Date: Mon, 30 Sep 2002 06:38:00 -0000	[thread overview]
Message-ID: <20020930133819.25401.qmail@sources.redhat.com> (raw)

Synopsis: arm-elf-gcc  generates undefined for __gxx_personality_sj0

State-Changed-From-To: open->closed
State-Changed-By: rearnsha
State-Changed-When: Mon Sep 30 06:38:17 2002
State-Changed-Why:
    The cited source files to reproduce this problem are missing.
    
    Gcc 3.0 was not really functional on the ARM.  If this problem still persists with the current sources (or 3.2) then please resubmit, remembering with a reproducible example.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4702


                 reply	other threads:[~2002-09-30 13:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020930133819.25401.qmail@sources.redhat.com \
    --to=rearnsha@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rslaughter@anatel.com \
    /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).