public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/14295] [tree-ssa] copy propagation for aggregates
Date: Sun, 22 Jun 2008 15:06:00 -0000	[thread overview]
Message-ID: <20080622150533.18528.qmail@sourceware.org> (raw)
In-Reply-To: <bug-14295-1008@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from rguenth at gcc dot gnu dot org  2008-06-22 15:05 -------
If we would disallow struct copies in the gimple IL and instead require a
register temporary that we would re-write into SSA form like

  struct s temp_struct3;
  struct s temp_struct2;
  struct s temp_struct1;
  struct s temp_struct3.3;
  struct s temp_struct2.2;
  struct s temp_struct1.1;
  struct s r.0;

<bb 2>:
  r.0_1 = r;
  temp_struct1 ={v} r.0_1;
  temp_struct1.1_2 = temp_struct1;
  temp_struct2 ={v} temp_struct1.1_2;
  temp_struct2.2_3 = temp_struct2;
  temp_struct3 ={v} temp_struct2.2_3;
  temp_struct3.3_4 = temp_struct3;
  <retval> ={v} temp_struct3.3_4;
  return <retval>;

then value-numbering can recognize the redundant copies and we end up
with

  struct s temp_struct3.3;
  struct s r.0;

<bb 2>:
  r.0_1 = r;
  <retval> = r.0_1;
  return <retval>;

(and of course with the possibility of out-of-SSA having to deal with
overlapping life-ranges of struct-typed SSA names)


-- 


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


  parent reply	other threads:[~2008-06-22 15:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-14295-1008@http.gcc.gnu.org/bugzilla/>
2006-01-07 18:04 ` steven at gcc dot gnu dot org
2006-01-14 12:16 ` rguenth at gcc dot gnu dot org
2006-02-14 15:53 ` rguenth at gcc dot gnu dot org
2006-03-10 15:34 ` dnovillo at gcc dot gnu dot org
2008-01-27 15:36 ` rguenth at gcc dot gnu dot org
2008-06-22 15:06 ` rguenth at gcc dot gnu dot org [this message]
2008-06-22 15:07 ` rguenth at gcc dot gnu dot org
     [not found] <bug-14295-4@http.gcc.gnu.org/bugzilla/>
2024-05-24 13:50 ` pinskia at gcc dot gnu.org
2004-02-25 17:37 [Bug optimization/14295] New: " dann at godzilla dot ics dot uci dot edu
2004-05-27  5:28 ` [Bug tree-optimization/14295] " pinskia at gcc dot gnu dot org
2004-06-29 17:41 ` pinskia at gcc dot gnu dot org
2005-09-14 17:35 ` 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=20080622150533.18528.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: 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).