public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46904] [4.6 Regression] g++.dg/tree-prof/(indir-call-prof.C|inline_mismatch_args.C) fail on powerpc-apple-darwin9 Date: Mon, 13 Dec 2010 09:24:00 -0000 [thread overview] Message-ID: <bug-46904-4-AmXkVRC1JL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46904-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46904 Iain Sandoe <iains at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|powerpc-apple-darwin9 |*-apple-darwin9 Status|UNCONFIRMED |NEW Last reconfirmed| |2010.12.13 09:23:54 CC| |hubicka at ucw dot cz Host|powerpc-apple-darwin9 |*-apple-darwin9 Ever Confirmed|0 |1 Build|powerpc-apple-darwin9 |*-apple-darwin9 --- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> 2010-12-13 09:23:54 UTC --- this also appears on i686-darwin9. the weak symbol errors appear with: http://gcc.gnu.org/ml/gcc-cvs/2010-11/msg00974.html I guess, if a symbol is artificially weakened - then one must recall section_for_xxxxx() because, at least on Darwin, weak symbols can only appear in [linker] coalesce-able sections. Honza?
next prev parent reply other threads:[~2010-12-13 9:24 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-12 13:42 [Bug c++/46904] New: " dominiq at lps dot ens.fr 2010-12-13 9:24 ` iains at gcc dot gnu.org [this message] 2010-12-16 14:37 ` [Bug c++/46904] " rguenth at gcc dot gnu.org 2010-12-20 10:01 ` iains at gcc dot gnu.org 2011-01-03 20:57 ` rguenth at gcc dot gnu.org 2011-01-09 19:04 ` howarth at nitro dot med.uc.edu 2011-01-09 21:02 ` dominiq at lps dot ens.fr
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-46904-4-AmXkVRC1JL@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: 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).