public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/19633] New: local address incorrectly thought to escape
Date: Tue, 25 Jan 2005 23:22:00 -0000 [thread overview]
Message-ID: <20050125232202.19633.rth@gcc.gnu.org> (raw)
struct S { int w, x, y, z; };
struct T { int r; struct S s; };
void bar (struct S, int);
void foo (int a, struct T b)
{
struct S *c = 0;
if (a)
c = &b.s;
bar (*c, a);
}
The call to bar appears to not be marked [tail-call] because b is marked
as a call-clobbered local variable. Which IIRC means that the aliasing code
thinks that the address of b escapes. Which is untrue -- no address escapes
from this function.
--
Summary: local address incorrectly thought to escape
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: rth at gcc dot gnu dot org
CC: dnovillo at gcc dot gnu dot org,gcc-bugs at gcc dot gnu
dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19633
next reply other threads:[~2005-01-25 23:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 23:22 rth at gcc dot gnu dot org [this message]
2005-01-25 23:26 ` [Bug tree-optimization/19633] " steven at gcc dot gnu dot org
2005-01-25 23:33 ` steven at gcc dot gnu dot org
2005-01-26 23:34 ` dnovillo at gcc dot gnu dot org
2005-01-27 4:45 ` cvs-commit at gcc dot gnu dot org
2005-01-27 4:58 ` dnovillo at gcc dot gnu dot org
2005-01-30 20:51 ` steven at gcc dot gnu dot org
2005-02-01 20:30 ` cvs-commit at gcc dot gnu dot org
2005-02-18 14:32 ` pinskia at gcc dot gnu dot org
2005-05-21 12:52 ` pinskia at gcc dot gnu dot org
2005-06-13 13:41 ` steven at gcc dot gnu dot org
2005-06-13 13:45 ` dnovillo at redhat dot com
2005-06-13 13:47 ` pinskia at gcc dot gnu dot org
2005-06-18 23: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=20050125232202.19633.rth@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).