public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastian.huber@embedded-brains.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50883] [ARM] Suboptimal optimization for small structures
Date: Thu, 27 Oct 2011 15:20:00 -0000	[thread overview]
Message-ID: <bug-50883-4-o9wQqkeK8R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50883-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50883

--- Comment #5 from Sebastian Huber <sebastian.huber@embedded-brains.de> 2011-10-27 15:19:57 UTC ---
If we look at the function f (the function g is similar):

struct s {
  int alignment;
  unsigned char a;
  unsigned char b;
  unsigned char c;
  unsigned char d;
};

unsigned f(struct s x)
{
  return x.a | (x.b << 8) | (x.c << 16) | (x.d << 24);
}

Currently ARM GCC produces this:

f:
    sub    sp, sp, #8
    add    r3, sp, #8
    stmdb    r3, {r0, r1}
    ldrb    r0, [sp, #6]
    ldrb    r3, [sp, #5]
    lsls    r0, r0, #16
    ldrb    r2, [sp, #4]
    orr    r0, r0, r3, lsl #8
    ldrb    r3, [sp, #7]
    orrs    r0, r0, r2
    orr    r0, r0, r3, lsl #24
    add    sp, sp, #8
    bx    lr

According to the ARM EABI, this structure is passed in registers r0 and r1. 
The return value is in r0.  This function may be reduced to:

f:
    mov    r0, r1
    bx    lr

The PowerPC GCC performs this optimization.


  parent reply	other threads:[~2011-10-27 15:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 11:55 [Bug target/50883] New: " sebastian.huber@embedded-brains.de
2011-10-27 11:56 ` [Bug target/50883] " sebastian.huber@embedded-brains.de
2011-10-27 11:58 ` sebastian.huber@embedded-brains.de
2011-10-27 11:58 ` sebastian.huber@embedded-brains.de
2011-10-27 14:51 ` rguenth at gcc dot gnu.org
2011-10-27 15:20 ` sebastian.huber@embedded-brains.de [this message]
2011-10-27 16:53 ` rearnsha at gcc dot gnu.org
2022-02-04  0:50 ` pinskia at gcc dot gnu.org
2022-02-04  0:50 ` pinskia at gcc dot gnu.org
2022-02-04 11:05 ` rearnsha at gcc dot gnu.org
2022-02-04 11:11 ` pinskia at gcc dot gnu.org
2022-02-04 11:30 ` rguenth at gcc dot gnu.org
2022-02-04 11:45 ` ebotcazou at gcc dot gnu.org
2022-02-04 11:58 ` rguenther at suse dot de
2022-02-04 12:24 ` ebotcazou at gcc dot gnu.org
2022-02-04 12:27 ` rearnsha at gcc dot gnu.org
2022-02-04 12:29 ` rearnsha at gcc dot gnu.org
2022-02-04 12:55 ` ebotcazou at gcc dot gnu.org
2022-02-04 16:29 ` sebastian.huber@embedded-brains.de

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-50883-4-o9wQqkeK8R@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: link
Be 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).