public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/58622] With -fomit-frame-pointer, A64 does not generate post-decrement stores Date: Thu, 20 Mar 2014 19:18:00 -0000 [thread overview] Message-ID: <bug-58622-4-gptWSzngh7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58622-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58622 Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |ramana at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |mshawcroft at gcc dot gnu.org --- Comment #3 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> --- (In reply to Kugan from comment #2) > Created attachment 32342 [details] > Proposed RFC patch > > Proposed RFC patch - In the process rgression testing. Kugan, This also needs to handle ILP32 and probably needs a bit more TLC than just this. We have something ongoing that can help address this, so assigning to Marcus as he's been looking into some of this. However this is stage1 material and cannot make it in for 4.9. Ramana (In reply to Kugan from comment #2) > Created attachment 32342 [details] > Proposed RFC patch > > Proposed RFC patch - In the process rgression testing.
next prev parent reply other threads:[~2014-03-20 19:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-04 18:24 [Bug target/58622] New: " b.grayson at samsung dot com 2014-01-28 15:23 ` [Bug target/58622] " rearnsha at gcc dot gnu.org 2014-03-13 3:24 ` kuganv at linaro dot org 2014-03-20 19:18 ` ramana at gcc dot gnu.org [this message] 2014-07-24 14:54 ` mshawcroft at gcc dot gnu.org 2014-07-24 14:54 ` mshawcroft 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-58622-4-gptWSzngh7@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).