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/48941] [arm gcc] NEON: Stack pointer operations performed even tho stack is not accessed at all in function. Date: Fri, 27 Jan 2012 17:12:00 -0000 [thread overview] Message-ID: <bug-48941-4-flDPiVFaQT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48941-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48941 --- Comment #9 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> 2012-01-27 16:20:07 UTC --- (In reply to comment #8) > Any chance of seeing the work on this restart ? > > I found this bug while looking for something that would help (I raised bug > 51980 for the same kind of issue, still seen on trunk), but the patch attached > to this bug does not solve the issue for code that is rich with zip/uzp/trn > intrinsics. I took a look at this for sometime when I was reviewing the patch submitted on trunk. The problem in this case appears to go away with -fno-split-wide-types but that in general is not a good idea. IIRC when RichardS and I talked about it we did talk about maybe getting lower-subreg to pay some attention to it. Neon intrinsics have been improving ( I'd like to think) over time but they are still not perfect unfortunately. I don't have time to look at this in the near term myself. > > This is a major limitation of arm-gcc with respect to performance-critical Neon > code in my opinion. As they say, patches are welcome :) Ramana
next prev parent reply other threads:[~2012-01-27 16:21 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-10 3:13 [Bug target/48941] New: " julien at cayzac dot name 2011-05-12 7:26 ` [Bug target/48941] " ramana at gcc dot gnu.org 2011-05-12 7:39 ` rsandifo at gcc dot gnu.org 2011-05-12 9:22 ` rsandifo at gcc dot gnu.org 2011-05-16 9:07 ` rearnsha at gcc dot gnu.org 2011-06-02 13:41 ` rsandifo at gcc dot gnu.org 2011-11-24 11:35 ` rearnsha at gcc dot gnu.org 2012-01-18 12:06 ` rsandifo at gcc dot gnu.org 2012-01-27 14:40 ` eric.batut at allegorithmic dot com 2012-01-27 17:12 ` ramana at gcc dot gnu.org [this message] 2012-05-02 6:29 ` ramana at gcc dot gnu.org 2012-05-02 6:52 ` ramana at gcc dot gnu.org 2012-05-22 14:40 ` ramana at gcc dot gnu.org 2012-07-05 16:57 ` ramana at gcc dot gnu.org 2012-07-05 17:02 ` ramana 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-48941-4-flDPiVFaQT@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).