public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carrot at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/40457] New: use stm and ldm to access consecutive memory words Date: Tue, 16 Jun 2009 09:07:00 -0000 [thread overview] Message-ID: <bug-40457-17659@http.gcc.gnu.org/bugzilla/> (raw) Current gcc can't make use of stm and ldm to reduce code size. -- Summary: use stm and ldm to access consecutive memory words Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: carrot at google dot com GCC build triplet: i686-linux GCC host triplet: i686-linux GCC target triplet: arm-eabi http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40457
next reply other threads:[~2009-06-16 9:07 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-16 9:07 carrot at google dot com [this message] 2009-06-16 9:11 ` [Bug target/40457] " carrot at google dot com 2009-06-16 10:04 ` ramana at gcc dot gnu dot org 2009-06-16 15:20 ` pinskia at gcc dot gnu dot org 2009-06-16 15:51 ` rearnsha at gcc dot gnu dot org 2009-06-16 18:17 ` ubizjak at gmail dot com 2009-06-17 8:41 ` rearnsha at arm dot com 2009-06-17 9:30 ` carrot at google dot com 2009-06-17 9:49 ` ramana at gcc dot gnu dot org 2009-06-19 10:18 ` ramana at gcc dot gnu dot org 2010-03-02 7:37 ` ramana at gcc dot gnu dot org 2010-03-02 11:15 ` jiez at gcc dot gnu dot org 2010-03-16 9:08 ` jiez at gcc dot gnu dot org 2010-04-20 11:47 ` bernds at codesourcery dot com 2010-08-02 10:07 ` bernds 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-40457-17659@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).