public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/16660] attribute((aligned)) doesn't work for variables on the stack for greater than required alignement
Date: Wed, 03 Oct 2007 22:08:00 -0000	[thread overview]
Message-ID: <20071003220752.31751.qmail@sourceware.org> (raw)
In-Reply-To: <bug-16660-1824@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from pinskia at gcc dot gnu dot org  2007-10-03 22:07 -------
Subject: Re:  attribute((aligned)) doesn't work for variables on the stack for
greater than required alignement

On 3 Oct 2007 22:04:28 -0000, hjl at lucon dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #7 from hjl at lucon dot org  2007-10-03 22:04 -------
> What is the performance impact of
>
> http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01167.html

The performance impact is non if the variables don't need aligned.
Otherwise you get a small penality at the very begining for the
alignment of the variable itself.  Really this is only to be used with
big alignments like 128byte alignment (for using with a DMA system
like in the Cell).

-- Pinski


-- 


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


  parent reply	other threads:[~2007-10-03 22:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16660-1824@http.gcc.gnu.org/bugzilla/>
2005-11-06  6:11 ` [Bug target/16660] attribute((aligned)) doesn't work for variables on the stack pinskia at gcc dot gnu dot org
2006-03-18 17:43 ` pinskia at gcc dot gnu dot org
2006-03-18 23:43 ` [Bug middle-end/16660] attribute((aligned)) doesn't work for variables on the stack for greater than required alignement sabre at nondot dot org
2006-09-06  7:14 ` thomas at reactsoft dot com
2007-01-13  1:58 ` pinskia at gcc dot gnu dot org
2007-10-03 22:04 ` hjl at lucon dot org
2007-10-03 22:08 ` pinskia at gcc dot gnu dot org [this message]
2007-10-03 22:17 ` hjl at lucon dot org
2007-10-03 22:27 ` hjl at lucon dot org
2007-10-03 22:41 ` pinskia at gcc dot gnu dot org
2007-10-04  0:02 ` hjl at lucon dot org
2008-01-03 18:01 ` pinskia at gcc dot gnu dot org
2008-07-31  1:05 ` hjl dot tools at gmail dot com
2008-07-31  1:07 ` pinskia at gcc dot gnu dot org
2009-03-05 14:03 ` hjl dot tools at gmail dot com
2009-04-16  9:22 ` nospamname at web dot de
2009-08-20  8:49 ` lessen42+gcc at gmail dot com
     [not found] <bug-16660-4@http.gcc.gnu.org/bugzilla/>
2010-10-01 23:04 ` pinskia at gcc dot gnu.org
2013-02-15  0:52 ` brooks at gcc dot gnu.org
2013-02-15  1:07 ` pinskia at gcc dot gnu.org
2013-02-15  1:12 ` brooks at gcc dot gnu.org
2014-02-05  8:40 ` kugel at rockbox dot org
2014-02-05  8:54 ` kugel at rockbox dot org
2014-02-16 10:03 ` jackie.rosen at hushmail dot com
2021-12-23  5:57 ` 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=20071003220752.31751.qmail@sourceware.org \
    --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).