public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19721] [meta-bug] optimizations that CSE still catches
Date: Thu, 09 May 2013 00:32:00 -0000	[thread overview]
Message-ID: <bug-19721-4-aNM9AwF2tL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-19721-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #26 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2013-05-09 00:32:28 UTC ---
The tree optimizers have become extremely aggressive on constant propagation,
so cse is needed more than ever to undo the damage.
With TARGET_LEGITIMATE_ADDRESS_P rejecting (costly) symbols_refs inside
memory references, cse_local brings the number of __malloc_av references down
when compiling newlib's malloc-r.c:
$ grep -c 'symbol_ref.*__malloc_av_' mallocr-4.4.i.*
mallocr-4.4.i.165r.expand:70
mallocr-4.4.i.166r.vregs:35
mallocr-4.4.i.167r.into_cfglayout:35
mallocr-4.4.i.168r.jump:70
mallocr-4.4.i.169r.subreg1:35
mallocr-4.4.i.170r.dfinit:35
mallocr-4.4.i.171r.cse1:70
mallocr-4.4.i.172r.fwprop1:41
mallocr-4.4.i.173r.cprop1:54
mallocr-4.4.i.175r.hoist:42
mallocr-4.4.i.176r.cprop2:30
mallocr-4.4.i.178r.cse_local:26


       reply	other threads:[~2013-05-09  0:32 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19721-4@http.gcc.gnu.org/bugzilla/>
2013-05-09  0:32 ` amylaar at gcc dot gnu.org [this message]
2013-05-09 10:40 ` steven at gcc dot gnu.org
2005-01-31 12:33 [Bug middle-end/19721] New: " steven at gcc dot gnu dot org
2005-01-31 12:35 ` [Bug middle-end/19721] " steven at gcc dot gnu dot org
2005-01-31 12:39 ` steven at gcc dot gnu dot org
2005-01-31 12:40 ` kazu at cs dot umass dot edu
2005-01-31 12:43 ` steven at gcc dot gnu dot org
2005-01-31 12:44 ` steven at gcc dot gnu dot org
2005-01-31 15:15 ` pinskia at gcc dot gnu dot org
2005-01-31 15:24 ` dnovillo at gcc dot gnu dot org
2005-01-31 15:27 ` dnovillo at gcc dot gnu dot org
2005-01-31 20:14 ` stevenb at suse dot de
2005-01-31 21:36 ` law at redhat dot com
2005-02-02  9:22 ` stevenb at suse dot de
2005-02-02 11:51 ` hubicka at ucw dot cz
2005-02-06 17:41 ` steven@gcc.gnu.org
2005-02-14  0:21 ` kazu at cs dot umass dot edu
2005-02-22  6:13 ` kazu at cs dot umass dot edu
2005-02-22  7:29 ` kazu at cs dot umass dot edu
2005-02-25 22:40 ` kazu at cs dot umass dot edu
2005-03-02 11:50 ` steven at gcc dot gnu dot org
2005-03-02 18:24 ` law at redhat dot com
2005-03-05 10:40 ` stevenb at suse dot de
2005-03-06  0:33 ` steven at gcc dot gnu dot org
2005-03-06  5:59 ` law at redhat dot com
2005-03-06  9:31 ` stevenb at suse dot de
2005-03-06 19:57 ` law at redhat dot com
2005-03-06 22:14 ` steven at gcc dot gnu dot org
2005-03-11  5:04 ` phython at gcc dot gnu dot org
2005-03-11 19:43 ` amylaar at gcc dot gnu dot org
2005-03-11 19:59 ` pinskia at gcc dot gnu dot org
2005-03-16 14:53 ` kazu at cs dot umass dot edu
2005-03-17  8:22 ` aoliva at gcc dot gnu dot org
2005-04-13 18:11 ` pinskia at gcc dot gnu dot org
2005-04-13 18:15 ` pinskia at gcc dot gnu dot org
2005-04-16 15:15 ` steven at gcc dot gnu dot org
2005-04-26 17:35 ` bonzini at gcc dot gnu dot org
2005-05-06 14:02 ` pinskia at gcc dot gnu dot org
2005-07-19 14:13 ` falk at debian dot org
2005-08-17  8:04 ` bonzini at gcc dot gnu dot org
2005-08-17 19:42 ` law at redhat dot com
2005-08-17 20:18 ` paolo dot bonzini at lu dot unisi dot ch
2005-08-18  7:56 ` bonzini at gcc dot gnu dot org
2005-09-16  8:10 ` steven at gcc dot gnu dot org
2005-09-29 12:40 ` 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=bug-19721-4-aNM9AwF2tL@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).