public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/17667] New: Const/pure function detection during tree-based profiling Date: Sat, 25 Sep 2004 11:00:00 -0000 [thread overview] Message-ID: <20040925110046.17667.giovannibajo@libero.it> (raw) Jan Hubicka said: the problem is caused by tree profiling affecting const/pure function autodetection resulting in CFG missmatch in between profiling and feedback passs. As disucssed with Rth, all the alternatives of fixing this I can think of seems nasty and bit invasiave for 4.0. [...] http://gcc.gnu.org/ml/gcc-patches/2004-09/msg02641.html This should be revisited for 4.1 -- Summary: Const/pure function detection during tree-based profiling Product: gcc Version: 4.0.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P2 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: giovannibajo at libero dot it CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17667
next reply other threads:[~2004-09-25 11:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-25 11:00 giovannibajo at libero dot it [this message] 2004-09-25 11:01 ` [Bug middle-end/17667] " giovannibajo at libero dot it 2005-03-26 5:29 ` pinskia at gcc dot gnu dot org 2005-04-05 2:00 ` pinskia at gcc dot gnu dot org 2005-05-07 14:04 ` steven at gcc dot gnu dot org 2005-07-04 21:35 ` pinskia at gcc dot gnu dot org 2005-07-05 0:54 ` jh at suse dot cz 2005-09-23 12:21 ` hubicka at gcc dot gnu dot org 2005-09-23 12:48 ` pinskia 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=20040925110046.17667.giovannibajo@libero.it \ --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).