public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39137] [4.4 Regression] -mpreferred-stack-boundary=2 causes lots of dynamic realign
Date: Wed, 11 Mar 2009 21:13:00 -0000 [thread overview]
Message-ID: <20090311211250.14710.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39137-87@http.gcc.gnu.org/bugzilla/>
------- Comment #41 from jakub at gcc dot gnu dot org 2009-03-11 21:12 -------
Subject: Bug 39137
Author: jakub
Date: Wed Mar 11 21:12:33 2009
New Revision: 144792
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=144792
Log:
PR target/39137
* cfgexpand.c (get_decl_align_unit): Use LOCAL_DECL_ALIGNMENT
macro.
* defaults.h (LOCAL_DECL_ALIGNMENT): Define if not yet defined.
* config/i386/i386.h (LOCAL_DECL_ALIGNMENT): Define.
* config/i386/i386.c (ix86_local_alignment): For
-m32 -mpreferred-stack-boundary=2 use 32-bit alignment for
long long variables on the stack to avoid dynamic realignment.
Allow the first argument to be a decl rather than type.
* doc/tm.texi (LOCAL_DECL_ALIGNMENT): Document.
* gcc.target/i386/stackalign/longlong-1.c: New test.
* gcc.target/i386/stackalign/longlong-2.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/stackalign/longlong-1.c
trunk/gcc/testsuite/gcc.target/i386/stackalign/longlong-2.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cfgexpand.c
trunk/gcc/config/i386/i386.c
trunk/gcc/config/i386/i386.h
trunk/gcc/defaults.h
trunk/gcc/doc/tm.texi
trunk/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39137
next prev parent reply other threads:[~2009-03-11 21:13 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 14:36 [Bug target/39137] New: " jakub at gcc dot gnu dot org
2009-02-09 14:37 ` [Bug target/39137] " jakub at gcc dot gnu dot org
2009-02-09 14:39 ` rguenth at gcc dot gnu dot org
2009-02-09 14:57 ` hjl dot tools at gmail dot com
2009-02-09 15:06 ` jakub at gcc dot gnu dot org
2009-02-09 15:21 ` hjl dot tools at gmail dot com
2009-02-10 20:32 ` hjl dot tools at gmail dot com
2009-02-10 20:48 ` jakub at gcc dot gnu dot org
2009-02-10 21:02 ` hjl dot tools at gmail dot com
2009-02-10 21:15 ` hjl dot tools at gmail dot com
2009-02-10 22:29 ` hjl dot tools at gmail dot com
2009-02-11 1:03 ` Joey dot ye at intel dot com
2009-02-11 8:43 ` ubizjak at gmail dot com
2009-02-11 14:39 ` hjl dot tools at gmail dot com
2009-02-11 22:11 ` pinskia at gcc dot gnu dot org
2009-02-12 8:03 ` jakub at gcc dot gnu dot org
2009-02-12 16:47 ` hubicka at gcc dot gnu dot org
2009-02-12 17:01 ` hjl dot tools at gmail dot com
2009-02-12 18:23 ` ubizjak at gmail dot com
2009-02-12 21:18 ` jakub at gcc dot gnu dot org
2009-02-13 19:15 ` jakub at gcc dot gnu dot org
2009-02-17 9:18 ` Joey dot ye at intel dot com
2009-02-17 9:29 ` jakub at gcc dot gnu dot org
2009-02-17 14:52 ` hjl dot tools at gmail dot com
2009-02-17 15:25 ` jakub at gcc dot gnu dot org
2009-02-17 15:41 ` hjl dot tools at gmail dot com
2009-02-17 17:29 ` hjl dot tools at gmail dot com
2009-02-21 13:00 ` hubicka at gcc dot gnu dot org
2009-02-21 13:06 ` rguenth at gcc dot gnu dot org
2009-02-21 15:38 ` hjl dot tools at gmail dot com
2009-02-22 18:47 ` hubicka at gcc dot gnu dot org
2009-02-22 19:28 ` hjl dot tools at gmail dot com
2009-02-23 3:15 ` Joey dot ye at intel dot com
2009-03-03 10:36 ` jakub at gcc dot gnu dot org
2009-03-03 14:48 ` hjl dot tools at gmail dot com
2009-03-03 16:01 ` jakub at gcc dot gnu dot org
2009-03-04 1:41 ` Joey dot ye at intel dot com
2009-03-11 14:47 ` rguenth at gcc dot gnu dot org
2009-03-11 16:26 ` jakub at gcc dot gnu dot org
2009-03-11 17:14 ` jakub at gcc dot gnu dot org
2009-03-11 17:18 ` hjl dot tools at gmail dot com
2009-03-11 20:04 ` rguenth at gcc dot gnu dot org
2009-03-11 21:13 ` jakub at gcc dot gnu dot org [this message]
2009-03-11 21:23 ` jakub at gcc dot gnu dot org
2009-03-12 0:41 ` howarth at nitro dot med dot uc dot edu
2009-03-12 0:44 ` hjl dot tools at gmail dot com
2009-03-12 0:46 ` howarth at nitro dot med dot uc dot edu
2009-03-12 0:47 ` howarth at nitro dot med dot uc dot edu
2009-03-12 6:52 ` Joey dot ye at intel dot com
2009-03-12 9:43 ` rguenth at gcc dot gnu dot org
2009-03-12 13:31 ` hjl dot tools at gmail dot com
2009-03-13 17:05 ` janis at gcc dot gnu dot org
2009-03-13 17:11 ` hjl dot tools at gmail dot com
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=20090311211250.14710.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).