public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldot at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/65534] tailcall not optimized away
Date: Thu, 09 Jul 2015 13:21:00 -0000 [thread overview]
Message-ID: <bug-65534-4-bHT8ufV12j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65534-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65534
--- Comment #2 from Bernhard Reutner-Fischer <aldot at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #1)
> > #ifndef OPTIMIZE_MANUALLY
> > void setutent(void) {
> > ((void)0);
> > __setutent_unlocked();
> > ((void)0);
> > }
> > #else
> > extern __typeof (__setutent_unlocked) setutent
> > __attribute__ ((alias ("__setutent_unlocked")));
> > #endif
>
> I do not think GCC can safely optimize this, becuase in the first
> case &setutent != &__setutent_unlocked, wile in the optimized
> case the addresses are equal.
Note that __setutent_unlocked is static, so i don't see how this specific case
would prevent optimization?
next prev parent reply other threads:[~2015-07-09 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 2:19 [Bug c/65534] New: " aldot at gcc dot gnu.org
2015-03-24 7:12 ` [Bug middle-end/65534] " hubicka at ucw dot cz
2015-03-24 7:21 ` hubicka at gcc dot gnu.org
2015-07-09 13:21 ` aldot at gcc dot gnu.org [this message]
2021-05-04 12:31 ` rguenth at gcc dot gnu.org
2023-03-31 11:56 ` marxin at gcc dot gnu.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=bug-65534-4-bHT8ufV12j@http.gcc.gnu.org/bugzilla/ \
--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).