public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chrbr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/53621] [SH] Frame pointers not generated with -fno-omit-frame-pointer on GCC 4.7.0
Date: Wed, 13 Jun 2012 07:45:00 -0000 [thread overview]
Message-ID: <bug-53621-4-elCtnzXdqB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53621-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53621
--- Comment #14 from chrbr at gcc dot gnu.org 2012-06-13 07:45:37 UTC ---
l(In reply to comment #13)
> I thought that the test depends the optimization level and it assumes
> -O0. I agree that enforcing -fomit-frame-pointer gives more deterministic
> result, though it could break current tunings for various targets.
> It would be better to ask it on the list.
This change can be made SH specific.
Index: gcc.dg/stack-usage-1.c
===================================================================
--- gcc.dg/stack-usage-1.c (revision 2720)
+++ gcc.dg/stack-usage-1.c (working copy)
@@ -1,5 +1,6 @@
/* { dg-do compile } */
/* { dg-options "-fstack-usage" } */
+/* { dg-options "-fomit-frame-pointer" { target { sh-*-* } } } */
/* This is aimed at testing basic support for -fstack-usage in the back-ends.
See the SPARC back-end for an example (grep flag_stack_usage in sparc.c).
Does this patch require another approval than yours ?
thanks
Christian
next prev parent reply other threads:[~2012-06-13 7:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 22:58 [Bug target/53621] New: " bluecrab2887 at netscape dot net
2012-06-10 2:29 ` [Bug target/53621] " lsebald1 at umbc dot edu
2012-06-10 19:13 ` olegendo at gcc dot gnu.org
2012-06-10 22:25 ` lsebald1 at umbc dot edu
2012-06-10 23:25 ` kkojima at gcc dot gnu.org
2012-06-11 13:49 ` chrbr at gcc dot gnu.org
2012-06-12 0:05 ` kkojima at gcc dot gnu.org
2012-06-12 6:25 ` chrbr at gcc dot gnu.org
2012-06-12 13:26 ` chrbr at gcc dot gnu.org
2012-06-12 13:56 ` kkojima at gcc dot gnu.org
2012-06-13 5:59 ` chrbr at gcc dot gnu.org
2012-06-13 6:52 ` kkojima at gcc dot gnu.org
2012-06-13 7:15 ` chrbr at gcc dot gnu.org
2012-06-13 7:39 ` kkojima at gcc dot gnu.org
2012-06-13 7:45 ` chrbr at gcc dot gnu.org [this message]
2012-06-13 7:47 ` chrbr at gcc dot gnu.org
2012-06-13 8:10 ` kkojima at gcc dot gnu.org
2012-06-13 8:23 ` chrbr at gcc dot gnu.org
2012-06-13 8:48 ` kkojima at gcc dot gnu.org
2012-06-14 8:38 ` chrbr at gcc dot gnu.org
2012-06-14 8:43 ` chrbr at gcc dot gnu.org
2012-06-14 8:55 ` chrbr at gcc dot gnu.org
2012-06-14 8:58 ` chrbr at gcc dot gnu.org
2012-06-20 7:11 ` ebotcazou at gcc dot gnu.org
2012-06-20 8:33 ` kkojima 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-53621-4-elCtnzXdqB@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).