public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uweigand at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/28862] [4.0/4.1/4.2 Regression] attribute ((aligned)) ignored on vector variables
Date: Tue, 05 Sep 2006 12:47:00 -0000	[thread overview]
Message-ID: <20060905124705.13646.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28862-1501@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from uweigand at gcc dot gnu dot org  2006-09-05 12:47 -------
(In reply to comment #5)
> Is this also supposed to fix the problem I posted in comment #2? I applied that
> patch to my gcc but it didn't fix the generated code for me. It's just weird
> because the bug only appears if the code is complex enough. If it's just a
> rather simple function, the generated code is correct.

No, your problem is certainly something completely different.  In fact I've
never seen GCC (common code) do anything even remotely like:
>GCC reserves an area big enough to hold the structure plus padding,
>so it can align the structure dynamically at runtime. It stores a
>pointer to the reserved area and a pointer to the structure within
>the area. 

Normally, attribute ((aligned)) does not cause any code to be
generated that attempts to dynamically adjust alignment at runtime,
it simply allows a variable to be aligned up to whatever default
stack frame alignment the platform ABI provides for.

It appears that the i386 back-end has some special code related to
the -mstackrealign option that may be involved here.  In any case,
this would be something for an i386 back-end person to look into.

Since this is a completely unrelated problem, I recommend you open
a separate bugzilla for it.


-- 


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


  parent reply	other threads:[~2006-09-05 12:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-26 22:22 [Bug c/28862] New: " uweigand at gcc dot gnu dot org
2006-08-26 22:29 ` [Bug middle-end/28862] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-09-01  7:10 ` thomas at reactsoft dot com
2006-09-01  8:05 ` thomas at reactsoft dot com
2006-09-01 22:06 ` mmitchel at gcc dot gnu dot org
2006-09-05  4:52 ` pinskia at gcc dot gnu dot org
2006-09-05  7:11 ` thomas at reactsoft dot com
2006-09-05 12:41 ` uweigand at gcc dot gnu dot org
2006-09-05 12:47 ` uweigand at gcc dot gnu dot org [this message]
2006-09-06  6:36 ` pinskia at gcc dot gnu dot org
2006-09-06  6:46 ` thomas at reactsoft dot com
2006-09-07  3:30 ` patchapp at dberlin dot org
2006-09-07 15:37 ` [Bug middle-end/28862] [4.0/4.1 " pinskia at gcc dot gnu dot org
2006-09-07 15:37 ` [Bug middle-end/28862] [4.0/4.1/4.2 " pinskia at gcc dot gnu dot org
2006-10-04  7:01 ` [Bug middle-end/28862] [4.0/4.1 " pinskia at gcc dot gnu dot org
2006-10-04  7:02 ` [Bug middle-end/28862] [4.0 " pinskia at gcc dot gnu dot org
2006-10-09  0:30 ` pinskia at gcc dot gnu dot org
2006-10-09  0:31 ` pinskia 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=20060905124705.13646.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).