public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dougmencken at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/43911] [4.4.3/4.5.0 regression] g++ can't compile any even trivial c++ source: undefined reference to `_Unwind_GetIPInfo'
Date: Tue, 27 Apr 2010 20:48:00 -0000	[thread overview]
Message-ID: <20100427204823.8092.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43911-18266@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from dougmencken at gmail dot com  2010-04-27 20:48 -------
And may I repeat, please? It's definitely not-x86[_64] bug. I don't know can it
be revealed with cross toolchain (because all of you do test gcc only and only
on x86[_64] as host).
So, if you don't have an access to real powerpc hardware, you can test it
in some emulator (like qemu). Also to reproduce you can try to
bootstrap native gcc > 4.4.2 on some real/emulated powerpc host (*not* i386 nor
i486 nor i586 nor i586mmx nor i686 nor x86_64 etc.).


-- 


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


  parent reply	other threads:[~2010-04-27 20:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 17:06 [Bug c++/43911] New: " dougmencken at gmail dot com
2010-04-27 17:15 ` [Bug c++/43911] " redi at gcc dot gnu dot org
2010-04-27 17:16 ` redi at gcc dot gnu dot org
2010-04-27 17:18 ` dougmencken at gmail dot com
2010-04-27 17:20 ` dougmencken at gmail dot com
2010-04-27 17:29 ` dougmencken at gmail dot com
2010-04-27 19:15 ` dougmencken at gmail dot com
2010-04-27 19:17 ` pinskia at gcc dot gnu dot org
2010-04-27 19:22 ` dougmencken at gmail dot com
2010-04-27 20:36 ` dougmencken at gmail dot com
2010-04-27 20:48 ` dougmencken at gmail dot com [this message]
2010-04-28  9:14 ` [Bug c++/43911] [4.4/4.5 Regression] " rguenth at gcc dot gnu dot org
2010-04-28  9:24 ` rguenth at gcc dot gnu dot org
2010-04-28 19:36 ` dougmencken at gmail dot com
2010-04-28 19:57 ` dougmencken at gmail dot com
2010-04-28 20:09 ` redi at gcc dot gnu dot org
2010-04-28 20:46 ` dougmencken at gmail dot com
2010-04-29  9:57 ` rguenth at gcc dot gnu dot org
2010-04-29 20:40 ` dougmencken at gmail dot com
2010-04-30  9:25 ` jakub at gcc dot gnu dot org
2010-05-02 13:30 ` dougmencken at gmail dot com
2010-05-10 14:03 ` dougmencken at gmail dot com
2010-05-10 16:24 ` dougmencken at gmail dot com
2010-05-10 16:31 ` pluto at agmk dot net
2010-05-10 17:28 ` redi at gcc dot gnu dot org
2010-05-11  5:53 ` dougmencken at gmail dot com
2010-05-11  6:51 ` mikpe at it dot uu dot se
2010-05-11 11:32 ` dougmencken at gmail dot com
2010-05-12 22:29 ` dougmencken at gmail dot com
2010-05-16  9:15 ` dougmencken at gmail dot com

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=20100427204823.8092.qmail@sourceware.org \
    --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).