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/23134] New: Address escapes even though the called function does not cause it to escape
Date: Fri, 29 Jul 2005 13:40:00 -0000	[thread overview]
Message-ID: <20050729134001.23134.pinskia@gcc.gnu.org> (raw)

Take this "stupid" example (even though this most likely shows up in GCC but I don't know for sure):
int g1(int);
static void h(int *a) { *a = 1; }

int g(void)
{
  int t = 0;
  h(&t);
  int t1 = t;
  g1(t1);
  return t1 == t;
}

That return should have been turned into "return 1" as t does not escape via h as h only touches it.
Compile with -O3 -fno-inline to see the problem.

-- 
           Summary: Address escapes even though the called function does not
                    cause it to escape
           Product: gcc
           Version: 4.1.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=23134


             reply	other threads:[~2005-07-29 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 13:40 pinskia at gcc dot gnu dot org [this message]
2005-07-29 13:43 ` [Bug tree-optimization/23134] " pinskia at gcc dot gnu dot org
2005-07-29 14:29 ` belyshev at depni dot sinp dot msu dot ru
2005-08-11 17:20 ` 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=20050729134001.23134.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).