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 optimization/13954] [tree-ssa] SRA does not work for classes that use inheritance
Date: Sat, 31 Jan 2004 21:23:00 -0000	[thread overview]
Message-ID: <20040131212356.29588.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040131211533.13954.dann@godzilla.ics.uci.edu>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-31 21:23 -------
Confirmed, the problem here is more complicated:
Cannot scalarize variable param because it must live in memory
Cannot scalarize variable local because it must live in memory
Cannot scalarize variable MT.3 because it must live in memory

The problem here is that:
void copystruct1(teststruct) (param)
{
  struct 
  {
    double d;
    char f1;
  } * local.0;
  struct 
  {
    double d;
    char f1;
  } * param.1;
  char T.2;

  {
    struct teststruct local;

    param.f1 = 0;
    local.0 = (struct 
    {
      double d;
      char f1;
    } *)&local;
    param.1 = (struct 
    {
      double d;
      char f1;
    } *)&param;
    *local.0 = *param.1;
    {
      T.2 = local.f1;
      if (T.2 != 0)
        {
          {
            link_error ();
          }
        }
      else
        {
          
        }
    }
  }
}

Which means it does not using the right structs assigning or something werid is going on.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
           Keywords|                            |pessimizes-code
   Last reconfirmed|0000-00-00 00:00:00         |2004-01-31 21:23:56
               date|                            |
   Target Milestone|---                         |tree-ssa


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


  reply	other threads:[~2004-01-31 21:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31 21:15 [Bug optimization/13954] New: " dann at godzilla dot ics dot uci dot edu
2004-01-31 21:23 ` pinskia at gcc dot gnu dot org [this message]
2004-02-01  0:04 ` [Bug optimization/13954] " dann at godzilla dot ics dot uci dot edu
2004-02-01  7:39 ` dnovillo at gcc dot gnu dot org
2004-02-03  3:25 ` rth at gcc dot gnu dot org
2004-02-23 16:29 ` pinskia at gcc dot gnu dot org
2004-05-15 16:25 ` [Bug c++/13954] " pinskia at gcc dot gnu dot org
2004-05-24 14:52 ` pinskia at gcc dot gnu dot org
2004-06-29 21:27 ` rth at gcc dot gnu dot org
2004-06-29 21:49 ` rth at gcc dot gnu dot org
2004-06-29 22:02 ` rth at gcc dot gnu dot org
2004-06-30  3:06 ` giovannibajo at libero dot it
2004-06-30 20:13 ` rth at gcc dot gnu dot org
2004-12-16  7:32 ` rth 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=20040131212356.29588.qmail@sources.redhat.com \
    --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).