public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63354] gcc -pg -mprofile-kernel creates unused stack frames on leaf functions on ppc64le
Date: Wed, 24 Sep 2014 14:31:00 -0000 [thread overview]
Message-ID: <bug-63354-4-ZOb6dfEHGN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63354-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63354
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|powerpc64le-linux |powerpc*-*-*
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-09-24
CC| |segher at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Confirmed. We need
#define TARGET_KEEP_LEAF_WHEN_PROFILED hook_bool_void_true
to have it behave as you want.
next prev parent reply other threads:[~2014-09-24 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 6:52 [Bug target/63354] New: " anton at samba dot org
2014-09-24 14:31 ` segher at gcc dot gnu.org [this message]
2014-09-25 1:45 ` [Bug target/63354] gcc " anton at samba dot org
2015-03-10 2:36 ` msebor 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-63354-4-ZOb6dfEHGN@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).