public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: deegan@mondes.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: debug/9984: ICE: GCC3.2.2 & GCC 3.2.1 gcc -gdwarf-2 -feliminate-dwarf2-dups Date: Thu, 06 Mar 2003 22:18:00 -0000 [thread overview] Message-ID: <20030306221803.28663.qmail@sources.redhat.com> (raw) Synopsis: ICE: GCC3.2.2 & GCC 3.2.1 gcc -gdwarf-2 -feliminate-dwarf2-dups State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Thu Mar 6 22:18:03 2003 State-Changed-Why: ICE confirmed with 3.2.2. With 3.3 and 3.4, the ICE goes away, but I get this: g/x> /home/bangerth/bin/gcc-3.4-pre/bin/gcc -gdwarf-2 -feliminate-dwarf2-dups x.cc /usr/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /tmp/cc4yE79M.o: In function `main': :4: undefined reference to `std::cout' :4: undefined reference to `std::basic_ostream<char, std::char_traits<char> >& std::operator<< <std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*)' :4: undefined reference to `std::basic_ostream<char, std::char_traits<char> >& std::endl<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&)' :4: undefined reference to `std::basic_ostream<char, std::char_traits<char> >::operator<<(std::basic_ostream<char, std::char_traits<char> >& (*)(std::basic_ostream<char, std::char_traits<char> >&))' /tmp/cc4yE79M.o: In function `__static_initialization_and_destruction_0(int, int)': /home/bangerth/bin/gcc-3.4-pre/include/c++/3.4/iostream:77: undefined reference to `std::ios_base::Init::Init[in-charge]()' /home/bangerth/bin/gcc-3.4-pre/include/c++/3.4/iostream:77: undefined reference to `std::ios_base::Init::~Init [in-charge]()' /tmp/cc4yE79M.o::4: undefined reference to `__gxx_personality_v0' collect2: ld returned 1 exit status The first few lines are probably due to an outdated set of binutils. I am in no position to judge the reason for the missing symbols, though. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9984
next reply other threads:[~2003-03-06 22:18 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-06 22:18 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-06 21:56 deegan
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=20030306221803.28663.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=deegan@mondes.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).