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++/41313] r150553 causes g++.dg/tree-prof/partition1.C compilation and execution test failures on *-apple-darwin*
Date: Mon, 05 Oct 2009 18:06:00 -0000 [thread overview]
Message-ID: <20091005180556.31861.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41313-11113@http.gcc.gnu.org/bugzilla/>
------- Comment #31 from howarth at nitro dot med dot uc dot edu 2009-10-05 18:05 -------
(In reply to comment #12)
> It is unclear what those labels are good for, but if darwin is to support
> hot/cold partitioning and FDEs covering it, the emit unwind_label hook (which
> is apparently darwin specific only) should be passed also the SECOND variable
> and create different label name for the second FDE for the same function (if
> function starts in hot section, then the second one is covering the cold
> section, and vice versa).
> The patch in #c11 would just mean you'd keep older versions broken.
>
Jakub,
Do you mean that we need to pass 'second' from gcc/ira-int.h?
/* Allocnos connected by the copy. The first allocno should have
smaller order number than the second one. */
ira_allocno_t first, second;
to darwin_emit_unwind_label()? Also, what would we use to detect whether the
first and second FDE's came from hot or cold sections?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41313
next prev parent reply other threads:[~2009-10-05 18:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 2:22 [Bug c++/41313] New: " howarth at nitro dot med dot uc dot edu
2009-09-10 3:49 ` [Bug c++/41313] " howarth at nitro dot med dot uc dot edu
2009-09-10 3:50 ` howarth at nitro dot med dot uc dot edu
2009-09-10 3:51 ` howarth at nitro dot med dot uc dot edu
2009-09-10 3:53 ` howarth at nitro dot med dot uc dot edu
2009-09-26 18:14 ` howarth at nitro dot med dot uc dot edu
2009-09-26 19:10 ` dominiq at lps dot ens dot fr
2009-09-26 20:20 ` hjl dot tools at gmail dot com
2009-09-26 20:43 ` rguenth at gcc dot gnu dot org
2009-09-30 20:26 ` howarth at nitro dot med dot uc dot edu
2009-09-30 20:54 ` mrs at apple dot com
2009-09-30 22:36 ` howarth at nitro dot med dot uc dot edu
2009-09-30 22:46 ` jakub at gcc dot gnu dot org
2009-10-01 0:18 ` howarth at nitro dot med dot uc dot edu
2009-10-01 0:29 ` howarth at nitro dot med dot uc dot edu
2009-10-01 0:54 ` mrs at apple dot com
2009-10-01 15:42 ` howarth at nitro dot med dot uc dot edu
2009-10-01 15:55 ` howarth at nitro dot med dot uc dot edu
2009-10-01 19:14 ` mrs at apple dot com
2009-10-01 23:54 ` howarth at nitro dot med dot uc dot edu
2009-10-02 2:03 ` mrs at apple dot com
2009-10-02 2:36 ` howarth at nitro dot med dot uc dot edu
2009-10-02 2:44 ` howarth at nitro dot med dot uc dot edu
2009-10-02 5:00 ` howarth at nitro dot med dot uc dot edu
2009-10-02 5:12 ` howarth at nitro dot med dot uc dot edu
2009-10-02 5:34 ` howarth at nitro dot med dot uc dot edu
2009-10-02 5:40 ` howarth at nitro dot med dot uc dot edu
2009-10-02 5:45 ` howarth at nitro dot med dot uc dot edu
2009-10-02 14:08 ` [Bug c++/41313] r150553 causes " howarth at nitro dot med dot uc dot edu
2009-10-02 22:10 ` howarth at nitro dot med dot uc dot edu
2009-10-04 16:38 ` howarth at nitro dot med dot uc dot edu
2009-10-05 18:06 ` howarth at nitro dot med dot uc dot edu [this message]
2009-10-05 20:55 ` mrs at apple dot com
2009-10-05 21:16 ` mrs at apple dot com
2009-10-05 23:25 ` howarth at nitro dot med dot uc dot edu
2009-10-06 0:52 ` howarth at nitro dot med dot uc dot edu
2009-10-06 2:03 ` howarth at nitro dot med dot uc dot edu
2009-10-06 2:06 ` howarth at nitro dot med dot uc dot edu
2009-10-06 2:18 ` howarth at nitro dot med dot uc dot edu
2009-10-06 2:19 ` howarth at nitro dot med dot uc dot edu
2009-10-08 15:17 ` howarth at nitro dot med dot uc dot edu
2009-10-08 15:17 ` howarth at nitro dot med dot uc dot edu
2009-10-11 1:12 ` howarth at nitro dot med dot uc dot edu
2009-10-11 1:13 ` howarth at nitro dot med dot uc dot edu
2009-10-21 15:08 ` pogma at gcc dot gnu dot org
2009-10-22 12:57 ` howarth at nitro dot med dot uc dot edu
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=20091005180556.31861.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).