public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jay.foad at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/58166] New: ARMv5: poor register allocation in function containing smull instruction Date: Thu, 15 Aug 2013 12:29:00 -0000 [thread overview] Message-ID: <bug-58166-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58166 Bug ID: 58166 Summary: ARMv5: poor register allocation in function containing smull instruction Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jay.foad at gmail dot com Created attachment 30660 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30660&action=edit C source for testcase On the attached test case I get: $ gcc -marm -S -O2 mul.c -o - -fomit-frame-pointer -march=armv5 ... mul: @ args = 0, pretend = 0, frame = 0 @ frame_needed = 0, uses_anonymous_args = 0 @ link register save eliminated. str r4, [sp, #-4]! smull r3, r4, r0, r1 mov r1, r4 mov r0, r3 ldr r4, [sp], #4 bx lr If the register allocator picked r2 and r3 for the result of the multiply, then there would be no need to push and pop r4. I'm using gcc built from svn r201719 configured with --target=arm-eabi.
next reply other threads:[~2013-08-15 12:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-15 12:29 jay.foad at gmail dot com [this message] 2013-08-21 14:29 ` [Bug target/58166] " rearnsha at gcc dot gnu.org 2013-08-21 15:14 ` jay.foad at gmail dot com 2013-08-22 10:24 ` jay.foad at gmail dot com 2013-08-22 14:03 ` rearnsha at gcc dot gnu.org 2013-08-22 14:11 ` rearnsha at gcc dot gnu.org 2013-08-25 14:16 ` vmakarov at redhat dot com 2024-03-28 5:08 ` pinskia 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-58166-4@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).