public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54731] New: arm-elf/arm-eabisim crosses fails in make-check due to undefined LFE refrences
Date: Thu, 27 Sep 2012 22:11:00 -0000	[thread overview]
Message-ID: <bug-54731-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 54731
           Summary: arm-elf/arm-eabisim crosses fails in make-check due to
                    undefined LFE refrences
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: bkoz@gcc.gnu.org


trunk sources, host is x86/linux, target is cross arm-elf or arm-eabisim has a
bunch of fails in libstdc++ due to unresolved references to ".LFE1602" etc
references.

These are keyed to out-of-line destructors (_ZThn8_NSt* mangled symbols) in:

strstream.o
sstream.o
iostream-inst.o
fstream-inst.o

this causes failed linking in the check-c++, check-libstdc++ testsuite.


             reply	other threads:[~2012-09-27 22:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 22:11 bkoz at gcc dot gnu.org [this message]
2012-09-28 12:50 ` [Bug debug/54731] [4.8 regression] arm-elf/arm-eabisim crosses fails in make-check due to undefined LFE references: corrupt debug_line tables rearnsha at gcc dot gnu.org
2012-09-29  3:59 ` bkoz at gcc dot gnu.org
2012-10-05 18:49 ` bkoz at gcc dot gnu.org
2012-11-25 15:52 ` rguenth at gcc dot gnu.org
2012-12-07 11:33 ` rguenth at gcc dot gnu.org
2012-12-18  8:38 ` jakub at gcc dot gnu.org
2012-12-18 15:19 ` ktkachov at gcc dot gnu.org
2012-12-18 16:37 ` jakub at gcc dot gnu.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-54731-4@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).