public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siarhei.siamashka at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/43725] Poor instructions selection, scheduling and registers allocation for ARM NEON intrinsics Date: Wed, 29 Jun 2011 13:35:00 -0000 [thread overview] Message-ID: <bug-43725-4-gMHz8skm9I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-43725-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43725 --- Comment #6 from Siarhei Siamashka <siarhei.siamashka at gmail dot com> 2011-06-29 13:35:13 UTC --- Created attachment 24630 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24630 test.c Attached a slightly updated testcase, which can demonstrate unnecessary spills to stack even with more recent versions of gcc as explained in comment 2 earlier (just slightly increased the number of uses for X() macro)
next prev parent reply other threads:[~2011-06-29 13:35 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-43725-4@http.gcc.gnu.org/bugzilla/> 2010-09-29 20:50 ` rearnsha at gcc dot gnu.org 2010-10-04 23:00 ` siarhei.siamashka at gmail dot com 2010-10-04 23:46 ` joseph at codesourcery dot com 2010-10-05 7:16 ` ramana at gcc dot gnu.org 2010-10-08 14:13 ` siarhei.siamashka at gmail dot com 2011-06-29 13:35 ` siarhei.siamashka at gmail dot com [this message] 2014-07-09 12:26 ` m.zakirov at samsung dot com 2014-07-29 11:35 ` m.zakirov at samsung dot com 2014-07-29 11:46 ` m.zakirov at samsung dot com 2014-08-20 16:44 ` mkuvyrkov at gcc dot gnu.org 2021-09-27 7:21 ` pinskia at gcc dot gnu.org 2010-04-12 7:27 [Bug target/43725] New: " siarhei dot siamashka at gmail dot com 2010-05-11 7:35 ` [Bug target/43725] " ramana at gcc dot gnu dot 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-43725-4-gMHz8skm9I@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).