public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/17863] [4.0/4.1/4.2/4.3 Regression] performance loss (not inlining as much??) Date: Sun, 21 Jan 2007 21:49:00 -0000 [thread overview] Message-ID: <20070121214950.29258.qmail@sourceware.org> (raw) In-Reply-To: <bug-17863-2109@http.gcc.gnu.org/bugzilla/> -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.1.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17863
next prev parent reply other threads:[~2007-01-21 21:49 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-17863-2109@http.gcc.gnu.org/bugzilla/> 2005-10-29 22:36 ` [Bug tree-optimization/17863] [4.0/4.1 Regression] threefold performance loss, not inlining as much steven at gcc dot gnu dot org 2005-10-31 0:37 ` mmitchel at gcc dot gnu dot org 2005-10-31 18:36 ` hubicka at gcc dot gnu dot org 2005-10-31 19:15 ` hubicka at gcc dot gnu dot org 2005-11-24 17:34 ` [Bug tree-optimization/17863] [4.0/4.1/4.2 " phython at gcc dot gnu dot org 2006-02-09 23:14 ` [Bug tree-optimization/17863] [4.0/4.1/4.2 Regression] performance loss (not inlining as much??) steven at gcc dot gnu dot org 2006-03-11 3:20 ` mmitchel at gcc dot gnu dot org 2007-01-18 3:06 ` [Bug tree-optimization/17863] [4.0/4.1/4.2/4.3 " gdr at gcc dot gnu dot org 2007-01-21 21:49 ` pinskia at gcc dot gnu dot org [this message] 2007-02-14 9:23 ` mmitchel at gcc dot gnu dot org 2007-12-18 20:02 ` steven at gcc dot gnu dot org 2008-01-30 17:35 ` hubicka at gcc dot gnu dot org 2008-01-30 18:27 ` hubicka at gcc dot gnu dot org 2008-01-30 18:34 ` hubicka at gcc dot gnu dot org 2008-01-30 20:41 ` stevenb dot gcc at gmail dot com 2008-01-31 1:13 ` hubicka at ucw dot cz 2008-01-31 10:00 ` rguenther at suse dot de 2008-02-01 16:48 ` hubicka at gcc dot gnu dot org 2008-02-01 17:46 ` amacleod at redhat dot com 2008-02-01 22:34 ` [Bug tree-optimization/17863] [4.0/4.1/4.2/4.3 Regression] performance loss (TER register presure and inlining limits problems) hubicka at gcc dot gnu dot org 2008-02-01 22:45 ` hubicka at ucw dot cz 2008-02-01 22:55 ` [Bug tree-optimization/17863] [4.0/4.1/4.2/4.3 Regression] performance loss (register pressure due to RA sucking " pinskia at gcc dot gnu dot org 2008-07-04 16:34 ` [Bug tree-optimization/17863] [4.2/4.3/4.4 Regression] performance loss performance loss (TER register presure " jsm28 at gcc dot gnu dot org 2009-02-08 11:50 ` [Bug tree-optimization/17863] [4.2/4.3/4.4 Regression] " hubicka at gcc dot gnu dot org 2009-03-31 16:20 ` [Bug tree-optimization/17863] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org 2009-08-04 12:27 ` rguenth at gcc dot gnu dot org 2009-12-28 15:40 ` steven at gcc dot gnu dot org 2010-03-21 12:13 ` steven 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=20070121214950.29258.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: 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).