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 rtl-optimization/28940] [4.1/4.2 Regression] address selection does not work correctly Date: Sat, 02 Sep 2006 21:29:00 -0000 [thread overview] Message-ID: <20060902212936.9647.qmail@sourceware.org> (raw) In-Reply-To: <bug-28940-10833@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2006-09-02 21:29 ------- Well actually this is just address section which goes funny. We use CSE at the rtl level do to some address mode selection (which I feel is wrong). Part of the reasons why we go funny is that we do the add in 32bit. What is happening with the other ones is the others are being converted into " return (&a[1])[i] + (&b[1])[i];" which are not converted back into a[i+1] and b[i+1] because I don't know but they should be. This is a regression because we do PRE/FRE at the tree level and let the address selection done at the rtl level (which is correct) but the rtl level address selectiong is not working to the level we need it to be for the regression not to show up. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|minor |normal Status|UNCONFIRMED |NEW Component|tree-optimization |rtl-optimization Ever Confirmed|0 |1 GCC build triplet|x86_64-redhat-linux | GCC host triplet|x86_64-redhat-linux | GCC target triplet|x86_64-redhat-linux |x86_64-*-*, i?86-*-* Keywords| |missed-optimization Last reconfirmed|0000-00-00 00:00:00 |2006-09-02 21:29:36 date| | Summary|Overzealous CSE with static |[4.1/4.2 Regression] address |array access |selection does not work | |correctly Target Milestone|--- |4.1.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28940
next prev parent reply other threads:[~2006-09-02 21:29 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-02 21:14 [Bug tree-optimization/28940] New: Overzealous CSE with static array access lmakhlis at bmc dot com 2006-09-02 21:29 ` pinskia at gcc dot gnu dot org [this message] 2006-09-07 1:16 ` [Bug rtl-optimization/28940] [4.1/4.2 Regression] address selection does not work correctly mmitchel at gcc dot gnu dot org 2006-09-07 8:11 ` bonzini at gnu dot org 2006-09-07 8:15 ` bonzini at gnu dot org 2006-09-09 5:48 ` [Bug rtl-optimization/28940] [4.0/4.1/4.2 " pinskia at gcc dot gnu dot org 2006-09-09 13:02 ` bonzini at gnu dot org 2006-09-09 13:03 ` bonzini at gnu dot org 2006-10-11 12:23 ` [Bug c/28940] " rguenth at gcc dot gnu dot org 2006-10-11 12:30 ` rguenth at gcc dot gnu dot org 2006-10-11 12:47 ` bonzini at gnu dot org 2006-10-11 12:53 ` rguenth at gcc dot gnu dot org 2006-10-11 13:05 ` paolo dot bonzini at lu dot unisi dot ch 2007-01-15 20:21 ` [Bug rtl-optimization/28940] " pinskia at gcc dot gnu dot org 2007-02-14 9:19 ` mmitchel at gcc dot gnu dot org 2007-07-05 10:37 ` bonzini at gnu dot org 2007-07-05 10:43 ` ebotcazou at gcc dot gnu dot org 2007-07-05 10:46 ` paolo dot bonzini at lu dot unisi dot ch 2007-11-03 7:53 ` ebotcazou at gcc dot gnu dot org 2007-11-03 7:54 ` ebotcazou 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=20060902212936.9647.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).