public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/26493] -freorder-blocks-and-partition is a dud without generated profiling data Date: Mon, 30 Dec 2013 19:07:00 -0000 [thread overview] Message-ID: <bug-26493-4-AnL9JKcYTg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-26493-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26493 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |avi@cloudius-systems.com --- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> --- *** Bug 59639 has been marked as a duplicate of this bug. ***
next parent reply other threads:[~2013-12-30 19:07 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-26493-4@http.gcc.gnu.org/bugzilla/> 2013-12-30 19:07 ` pinskia at gcc dot gnu.org [this message] 2013-12-30 19:12 ` mkgnu at mkgnu dot net 2013-12-30 19:21 ` mkgnu at mkgnu dot net 2013-12-30 19:31 ` mkgnu at mkgnu dot net 2013-12-30 20:39 ` mkgnu at mkgnu dot net 2006-02-28 8:26 [Bug c/26493] New: -freorder-blocks-and-partition is a dud arjanv at redhat dot com 2007-04-13 21:41 ` [Bug rtl-optimization/26493] -freorder-blocks-and-partition is a dud without generated profiling data steven at gcc dot gnu dot org 2007-04-24 19:27 ` pinskia at gcc dot gnu dot org 2007-04-25 1:12 ` mkgnu at mkgnu dot net 2007-04-30 22:42 ` mkgnu at mkgnu dot net 2007-04-30 22:49 ` 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=bug-26493-4-AnL9JKcYTg@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).