public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/14222] New: insufficient stack alignment
Date: Mon, 11 Jun 2012 19:03:00 -0000	[thread overview]
Message-ID: <bug-14222-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=14222

             Bug #: 14222
           Summary: insufficient stack alignment
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
        AssignedTo: unassigned@sourceware.org
        ReportedBy: jan.kratochvil@redhat.com
    Classification: Unclassified
            Target: i386-unknown-linux-gnu


GCC since 4.6 keeps stack aligned to 32 bytes (128 bits).
http://groups.google.com/group/ia32-abi/browse_thread/thread/4f9b3e5069943bf1

AFAIK there is neither Intel CPUs nor glibc requirement for it, 16 bytes
alignment would be sufficient.

amd64-tdep.c already keeps 16 byte alignment but i386-tdep.c does not.
Proposing to increase alignment of both to 32 bytes in all cases.

This is KFAIL tracker for: gdb.arch/i386-sse-stack-align.exp

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-06-11 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 19:03 jan.kratochvil at redhat dot com [this message]
2012-06-13 15:54 ` [Bug tdep/14222] " jan.kratochvil at redhat dot com
2012-06-13 21:21 ` cvs-commit at gcc dot gnu.org
2012-06-13 21:31 ` cvs-commit at gcc dot gnu.org
2012-06-13 21:32 ` jan.kratochvil at redhat 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-14222-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).