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 middle-end/23401] New: Gimplifier produces too many temporaries Date: Mon, 15 Aug 2005 15:18:00 -0000 [thread overview] Message-ID: <20050815150840.23401.pinskia@gcc.gnu.org> (raw) Take the following code: struct f { struct { int i; } ff[10]; }; struct f g; int ffff(int i) { int t1 = 0; int i1 = g.ff[t1].i; int i2 = g.ff[i].i; return i1 + i2; } The gimplfiier will produce at -O0: int i.0; int t1.1; int D.1289; int t1; int i1; int i2; t1 = 0; i.0 = i; i1 = g.ff[i.0].i; t1.1 = t1; i2 = g.ff[t1.1].i; D.1289 = i1 + i2; return D.1289; Notice how there is a t1.0 and i.0, there should not be there as i and t1 are already gimple variables. This might produce a nice speed up for some testcase but I don't know. at -O0, there will be less registers to be allocated so reload should not be as high as before. -- Summary: Gimplifier produces too many temporaries Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: minor Priority: P2 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23401
next reply other threads:[~2005-08-15 15:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-15 15:18 pinskia at gcc dot gnu dot org [this message] 2005-08-15 15:24 ` [Bug middle-end/23401] " pinskia at gcc dot gnu dot org 2005-08-15 15:25 ` pinskia at gcc dot gnu dot org 2005-08-15 15:45 ` pinskia at gcc dot gnu dot org 2005-08-31 16:05 ` 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=20050815150840.23401.pinskia@gcc.gnu.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).