public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernds at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65804] blackfin: Not support global frame pointer with -fno-omit-frame-pointer Date: Mon, 12 Oct 2015 22:43:00 -0000 [thread overview] Message-ID: <bug-65804-4-HomdEpbPXE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65804-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65804 Bernd Schmidt <bernds at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |bernds at gcc dot gnu.org Resolution|--- |INVALID --- Comment #3 from Bernd Schmidt <bernds at gcc dot gnu.org> --- This looks exactly like expected behaviour. Closing as not a bug.
prev parent reply other threads:[~2015-10-12 22:43 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65804-4@http.gcc.gnu.org/bugzilla/> 2015-09-03 2:47 ` gang.chen.5i5j at gmail dot com 2015-09-05 2:43 ` gang.chen.5i5j at gmail dot com 2015-10-12 22:43 ` bernds at gcc dot gnu.org [this message]
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-65804-4-HomdEpbPXE@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: linkBe 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).