public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yann at droneaud dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/57908] alignment of arrays allocated stack on amd64/x86_64: 16 bytes ?
Date: Tue, 16 Jul 2013 15:32:00 -0000	[thread overview]
Message-ID: <bug-57908-4-b4lF7k6Kmf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57908-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Yann Droneaud <yann at droneaud dot fr> ---
Using -Os show different results:

   Arrays                                                                
   object |       u8_0 |     0x7fff9b4c05bc |    1 |         4 |        1
   object |       u8_1 |     0x7fff9b4c05c7 |    3 |         1 |        1
   object |       u8_2 |     0x7fff9b4c05da |    7 |         2 |        1
   object |       u8_3 |     0x7fff9b4c05d0 |    5 |        16 |        1
   object |       u8_4 |     0x7fff9b4c05bf |    2 |         1 |        1
   object |       u8_5 |     0x7fff9b4c05bd |    1 |         1 |        1
   object |       u8_6 |     0x7fff9b4c05ca |    3 |         2 |        1
   object |       u8_7 |     0x7fff9b4c05d5 |    5 |         1 |        1
   object |       u8_8 |     0x7fff9b4c05e1 |    7 |         1 |        1
   object |       u8_9 |     0x7fff9b4c05c1 |    2 |         1 |        1
   object |      u8_10 |     0x7fff9b4c05e8 |   11 |         8 |        1
   object |      u8_11 |     0x7fff9b4c05cd |    3 |         1 |        1
   object |      u8_12 |     0x7fff9b4c05f3 |   13 |         1 |        1
   object |      u8_13 |     0x7fff9b4c05c3 |    2 |         1 |        1
   object |      u8_14 |     0x7fff9b4c05be |    1 |         2 |        1
   object |      u8_15 |     0x7fff9b4c05c5 |    2 |         1 |        1


So GCC is using 16 bytes to align array allocated on stack by default but it's
not enforcing such alignment.
I guess it's all about optimisation ... but wasting up to 14 bytes to get an
array of 2 bytes aligned might be overkill.

Could someone comment on which optimisation is achieved by aligning such small
arrays ?

Regards.


  parent reply	other threads:[~2013-07-16 15:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 14:35 [Bug c/57908] New: " yann at droneaud dot fr
2013-07-16 14:39 ` [Bug c/57908] " yann at droneaud dot fr
2013-07-16 15:03 ` pinskia at gcc dot gnu.org
2013-07-16 15:06 ` [Bug target/57908] " pinskia at gcc dot gnu.org
2013-07-16 15:11 ` yann at droneaud dot fr
2013-07-16 15:18 ` yann at droneaud dot fr
2013-07-16 15:20 ` yann at droneaud dot fr
2013-07-16 15:28 ` pinskia at gcc dot gnu.org
2013-07-16 15:32 ` yann at droneaud dot fr [this message]
2013-07-16 15:36 ` pinskia at gcc dot gnu.org
2013-07-16 15:56 ` yann at droneaud dot fr

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-57908-4-b4lF7k6Kmf@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).