public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/66697] Feature request: -mstackrealign and force_align_arg_pointer for x86_64
Date: Wed, 07 Oct 2015 17:42:00 -0000	[thread overview]
Message-ID: <bug-66697-4-1HhG0uEwnx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66697-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66697

--- Comment #25 from uros at gcc dot gnu.org ---
Author: uros
Date: Wed Oct  7 17:42:09 2015
New Revision: 228577

URL: https://gcc.gnu.org/viewcvs?rev=228577&root=gcc&view=rev
Log:
        PR target/66697
        * config/i386/i386.c (ix86_option_override_internal): Always use
        8-byte minimum stack boundary in 64-bit mode.
        (ix86_compute_frame_layout): Remove assert on INCOMING_STACK_BOUNDARY.
        (ix86_emit_save_reg_using_mov): Support unaligned SSE store.
        Add a REG_CFA_EXPRESSION note if needed.
        (ix86_emit_restore_sse_regs_using_mov): Support unaligned SSE load.
        (ix86_handle_force_align_arg_pointer_attribute): New.
        (ix86_minimum_incoming_stack_boundary): Remove TARGET_64BIT check.
        (ix86_attribute_table): Set ix86_force_align_arg_pointer_string
        with ix86_handle_force_align_arg_pointer_attribute.
        * config/i386/i386.h (MIN_STACK_BOUNDARY): Set to BITS_PER_WORD.

testsuite/ChangeLog:

        PR target/66697
        * gcc.target/i386/20060512-1.c: Remove ia32 requirement.
        (PUSH, POP): New defines.
        (sse2_test): Use PUSH and POP to misalign runtime stack.
        * gcc.target/i386/20060512-2.c: Remove ia32 requirement.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/i386.c
    trunk/gcc/config/i386/i386.h
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gcc.target/i386/20060512-1.c
    trunk/gcc/testsuite/gcc.target/i386/20060512-2.c


  parent reply	other threads:[~2015-10-07 17:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 20:03 [Bug target/66697] New: " bucaneer at gmail dot com
2015-09-29  4:26 ` [Bug target/66697] " austinenglish at gmail dot com
2015-10-04 15:29 ` ubizjak at gmail dot com
2015-10-04 21:23 ` bucaneer at gmail dot com
2015-10-05  9:08 ` ubizjak at gmail dot com
2015-10-05 17:40 ` ubizjak at gmail dot com
2015-10-05 19:55 ` bucaneer at gmail dot com
2015-10-06  6:40 ` ubizjak at gmail dot com
2015-10-06  9:21 ` ubizjak at gmail dot com
2015-10-06 12:33 ` bucaneer at gmail dot com
2015-10-06 13:45 ` ubizjak at gmail dot com
2015-10-06 16:38 ` bucaneer at gmail dot com
2015-10-06 16:42 ` ubizjak at gmail dot com
2015-10-06 16:53 ` ubizjak at gmail dot com
2015-10-06 23:09 ` bucaneer at gmail dot com
2015-10-07  6:51 ` ubizjak at gmail dot com
2015-10-07 10:49 ` hjl.tools at gmail dot com
2015-10-07 12:13 ` bucaneer at gmail dot com
2015-10-07 12:17 ` hjl.tools at gmail dot com
2015-10-07 12:21 ` ubizjak at gmail dot com
2015-10-07 17:42 ` uros at gcc dot gnu.org [this message]
2015-10-12 16:30 ` uros at gcc dot gnu.org
2015-10-12 16:42 ` ubizjak 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=bug-66697-4-1HhG0uEwnx@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).