public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bucaneer at gmail dot com" <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: Mon, 05 Oct 2015 19:55:00 -0000	[thread overview]
Message-ID: <bug-66697-4-h1jjE5uaK0@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 #8 from Justas L <bucaneer at gmail dot com> ---
I applied the first (testing) version of the patch on gcc 5.2.0 release source
(with slight modifications to make it apply). All new features work as
expected, as per the test in comment #2. However, compiling Wine with either
-mstackrealign or -mincoming-stack-boundary=3 fails, throwing this error:

---------
../../../wine/dlls/dxerr8/dxerr8.c:135:1: internal compiler error: in
ix86_compute_frame_layout, at config/i386/i386.c:10212
---------

which refers to this line in i386.c:

---------
gcc_assert (INCOMING_STACK_BOUNDARY >= 128);
---------

Commenting out the assert allows Wine to compile normally. (I assume the
correct fix would be to change the number to 64.) And compiling Wine with
-mincoming-stack-boundary=3 does fix the original issue (or at least the one
instance of it that I care about). So the gcc side of the issue is almost
resolved, with just the assert left to address.


  parent reply	other threads:[~2015-10-05 19:55 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 [this message]
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
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-h1jjE5uaK0@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).