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 tree-optimization/18546] New: tree vectorizer does not understand RETURN_DECL
Date: Thu, 18 Nov 2004 16:11:00 -0000	[thread overview]
Message-ID: <20041118161104.18546.pinskia@gcc.gnu.org> (raw)

Compile the following with the C and C++ front-end and you will get different assembly, the C front-
end does not do NVR at all while the C++ front-end will change the a decl to be the return_decl before 
so we the vectorizer cannot do the vectorization because it does not hanndle RETURN_DECLs at all.

struct A
{
    int x[4];
};

struct A foo()
{
  struct A a;
  for (int i=0; i<4; ++i)
    a.x[i] = 0;
  return a;
}

-- 
           Summary: tree vectorizer does not understand RETURN_DECL
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P2
         Component: tree-optimization
        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=18546


             reply	other threads:[~2004-11-18 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 16:11 pinskia at gcc dot gnu dot org [this message]
2004-11-20 18:41 ` [Bug tree-optimization/18546] " pinskia at gcc dot gnu dot org
2005-03-04 15:11 ` cjb at mrao dot cam dot ac dot uk
2005-03-04 15:19 ` pinskia at gcc dot gnu dot org
2005-03-05 15:53 ` cjb at mrao dot cam dot ac dot uk
2005-03-05 17:03 ` pinskia at gcc dot gnu dot org
2005-03-07 23:21 ` 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=20041118161104.18546.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: 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).