public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37843] [4.4 Regression] unaligned stack in main due to tail call optimization
Date: Tue, 25 Nov 2008 15:36:00 -0000	[thread overview]
Message-ID: <20081125153451.13418.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37843-682@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from hjl at gcc dot gnu dot org  2008-11-25 15:34 -------
Subject: Bug 37843

Author: hjl
Date: Tue Nov 25 15:33:27 2008
New Revision: 142193

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142193
Log:
gcc/

2008-11-25  H.J. Lu  <hongjiu.lu@intel.com>
            Joey Ye  <joey.ye@intel.com>

        PR middle-end/37843
        * config/i386/i386.c (ix86_function_ok_for_sibcall): Return
        false if we need to align the outgoing stack.
        (ix86_update_stack_boundary): Check parm_stack_boundary.

gcc/testsuite/

2008-11-25  H.J. Lu  <hongjiu.lu@intel.com>

        PR middle-end/37843
        * gcc.target/i386/align-main-3.c: New.
        * gcc.target/i386/pr37843-1.c: Likewise.
        * gcc.target/i386/pr37843-2.c: Likewise.
        * gcc.target/i386/pr37843-3.c: Likewise.

Added:
    trunk/gcc/testsuite/gcc.target/i386/align-main-3.c
    trunk/gcc/testsuite/gcc.target/i386/pr37843-1.c
    trunk/gcc/testsuite/gcc.target/i386/pr37843-2.c
    trunk/gcc/testsuite/gcc.target/i386/pr37843-3.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/i386.c
    trunk/gcc/testsuite/ChangeLog


-- 


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


  parent reply	other threads:[~2008-11-25 15:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16  0:49 [Bug target/37843] New: " hjl dot tools at gmail dot com
2008-10-16  1:08 ` [Bug target/37843] " hjl dot tools at gmail dot com
2008-10-16 22:16 ` hjl dot tools at gmail dot com
2008-10-30 22:56 ` hjl dot tools at gmail dot com
2008-11-01  0:27 ` [Bug middle-end/37843] " hjl dot tools at gmail dot com
2008-11-01 11:37 ` rguenth at gcc dot gnu dot org
2008-11-05 14:33 ` hjl dot tools at gmail dot com
2008-11-11  6:50 ` hjl dot tools at gmail dot com
2008-11-18 21:35 ` steven at gcc dot gnu dot org
2008-11-25 15:36 ` hjl at gcc dot gnu dot org [this message]
2008-11-26  4:26 ` howarth at nitro dot med dot uc dot edu
2008-11-26  4:28 ` howarth at nitro dot med dot uc dot edu
2008-11-26  4:29 ` howarth at nitro dot med dot uc dot edu
2008-11-26  5:40 ` hjl dot tools at gmail dot com
2008-11-26 12:24 ` howarth at nitro dot med dot uc dot edu
2008-11-26 14:55 ` hjl at gcc dot gnu dot org
2008-11-28 16:33 ` hjl at gcc dot gnu dot org
2008-11-29 16:35 ` hjl at gcc dot gnu dot org
2008-11-29 21:05 ` jakub at gcc dot gnu dot org
2008-11-29 21:12 ` hjl dot tools at gmail dot com
2008-11-30 11:21 ` rguenther at suse dot de
2008-12-09 19:36 ` mmitchel at gcc dot gnu dot org
2008-12-09 22:36 ` hjl dot tools at gmail dot com
2008-12-09 22:37 ` hjl dot tools at gmail dot com
2009-01-15 15:08 ` jakub at gcc dot gnu dot org
2009-01-15 15:18 ` hjl dot tools at gmail dot com
2009-01-15 15:23 ` dnovillo at gcc dot gnu dot org
2009-01-15 15:45 ` hjl at gcc dot gnu dot org
2009-01-15 16:29 ` jakub 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=20081125153451.13418.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).