public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/42070] New: FAIL: g++.dg/tree-prof/partition1.C compilation, -O3 -g -fprofile-use Date: Mon, 16 Nov 2009 20:00:00 -0000 [thread overview] Message-ID: <bug-42070-11113@http.gcc.gnu.org/bugzilla/> (raw) Currently in gcc trunk on darwin10, we fail the test cases... FAIL: g++.dg/tree-prof/partition1.C compilation, -g -fprofile-use UNRESOLVED: g++.dg/tree-prof/partition1.C execution, -g -fprofile-use FAIL: g++.dg/tree-prof/partition1.C compilation, -O3 -g -fprofile-use UNRESOLVED: g++.dg/tree-prof/partition1.C execution, -O3 -g -fprofile-use when compiling with -freorder-blocks-and-partition on darwin10 because of many warnings of the form... ld: warning: can't add line info to anonymous symbol anon-func-0xF40 from /var/tmp//ccrw73YL.o This was filed as radar 7289379 with the two failing test cases provided as samples of the problem. Apple's response was... "In the sample you supplied, the warning is because there is code in the __TEXT/__unlikely section and there is dwarf debug information that says it part of a function. The linker sanity checks how it broke up the .o file into "atoms" by checking it against the dwarf debug info. I think the __unlikely section should be avoided on darwin until it is shown to work with the linker. At a minimum each chunk in the __unlikely section should have a label on it with a name based on the function it came from. Those labels would also help debugging. This warning does not have anything to do removing labels from __eh_frame section." -- Summary: FAIL: g++.dg/tree-prof/partition1.C compilation, -O3 -g -fprofile-use Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: howarth at nitro dot med dot uc dot edu GCC build triplet: *-apple-darwin10 GCC host triplet: *-apple-darwin10 GCC target triplet: *-apple-darwin10 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42070
next reply other threads:[~2009-11-16 20:00 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-16 20:00 howarth at nitro dot med dot uc dot edu [this message] 2009-11-16 20:02 ` [Bug target/42070] " pinskia at gcc dot gnu dot org 2010-04-06 20:54 ` iains at gcc dot gnu dot org 2010-09-09 17:20 ` howarth at nitro dot med dot uc dot edu 2010-09-14 7:41 ` bonzini at gcc dot gnu dot org 2010-09-15 7:55 ` mrs at gcc dot gnu dot 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-42070-11113@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).