public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38134] [4.6/4.7/4.8 Regression] speed regression with many loop invariants
Date: Mon, 04 Feb 2013 14:47:00 -0000	[thread overview]
Message-ID: <bug-38134-4-Uyxay1fwJa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38134-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38134

--- Comment #20 from Richard Biener <rguenth at gcc dot gnu.org> 2013-02-04 14:47:31 UTC ---
Ok, the goal would be to have all !targetm.legitimate_constant_p () constants
assigned to a pseudo (and in GIMPLE to an SSA name).  One piece of code that
defeats that purpose is replace_uses_in called from tree CCP for example.
But in this case already fold () does it's job and expands all
static const initializers inline.

Of course that then suggests to move initial constant pool creation to
the gimple level instead.


  parent reply	other threads:[~2013-02-04 14:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38134-4@http.gcc.gnu.org/bugzilla/>
2010-10-01 12:11 ` [Bug target/38134] [4.4/4.5/4.6 " jakub at gcc dot gnu.org
2011-04-16 11:22 ` [Bug target/38134] [4.4/4.5/4.6/4.7 " jakub at gcc dot gnu.org
2012-01-05  0:35 ` pinskia at gcc dot gnu.org
2012-03-13 14:17 ` [Bug target/38134] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 12:20 ` rguenth at gcc dot gnu.org
2013-01-15 15:20 ` [Bug target/38134] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2013-02-04 14:47 ` rguenth at gcc dot gnu.org [this message]
2013-03-13 20:10 ` steven at gcc dot gnu.org
2013-04-12 15:17 ` [Bug target/38134] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-12-06 13:15 ` rguenth at gcc dot gnu.org
2014-06-12 13:45 ` [Bug target/38134] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:44 ` [Bug target/38134] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23  8:21 ` [Bug target/38134] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:10 ` [Bug target/38134] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:36 ` jakub at gcc dot gnu.org
2021-05-14  9:46 ` [Bug target/38134] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:04 ` rguenth at gcc dot gnu.org
2022-05-27  9:33 ` [Bug target/38134] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:29 ` jakub at gcc dot gnu.org
2023-07-07 10:29 ` [Bug target/38134] [11/12/13/14 " rguenth at gcc dot gnu.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-38134-4-Uyxay1fwJa@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: 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).