public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/62281] gcc doesn't conform to Solaris 32-bit ABI by expecting 16-byte stack alignment
Date: Fri, 29 Aug 2014 14:37:00 -0000	[thread overview]
Message-ID: <bug-62281-4-ulMGdaBxhd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62281-4@http.gcc.gnu.org/bugzilla/>

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

Rainer Orth <ro at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ro at gcc dot gnu.org
   Target Milestone|---                         |5.0

--- Comment #6 from Rainer Orth <ro at gcc dot gnu.org> ---
I've been seeing the same issue in PR middle-end/61949, but only on Solaris 10,
not S11, and the failures have been intermittent (i.e. happened during one
bootstrap,
but were gone a week later).

Regarding

> I believe the problem was fixed for the limited case of Solaris 9 x86 in bug 
> 60107. However, the analysis for this fix seems slightly off. It infers that,
> because Solaris 10 creates outgoing thread stacks aligned on 16 bytes, the
> 32-bit ABI has changed to 16-byte stack alignment on this platform, which isn't
> correct.

I believe the i386 psABI is irrelevant here: while it requires word alignment,
it
doesn't preclude that Solaris guarantees a stricter alignment, which from what
I've seen both S10 and S11 do.

> I suggest -mincoming-stack-boundary=2 should be the default for all 32-bit
> Solaris binaries.

Before making any changes in this area, I'd like word from the responsible libc
engineer (Roger Faulkner probably) what various Solaris versions do and don't
guarantee.

  Rainer


  parent reply	other threads:[~2014-08-29 14:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 10:55 [Bug target/62281] New: " justin.carveley at oracle dot com
2014-08-27 10:56 ` [Bug target/62281] " justin.carveley at oracle dot com
2014-08-27 10:57 ` justin.carveley at oracle dot com
2014-08-27 10:58 ` justin.carveley at oracle dot com
2014-08-27 10:59 ` justin.carveley at oracle dot com
2014-08-27 10:59 ` justin.carveley at oracle dot com
2014-08-29 14:37 ` ro at gcc dot gnu.org [this message]
2014-08-29 15:16 ` joseph at codesourcery dot com
2015-04-22 12:00 ` jakub at gcc dot gnu.org
2015-07-16  9:13 ` rguenth at gcc dot gnu.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=bug-62281-4-ulMGdaBxhd@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).