This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/49503] Incorrect stack alignment, produced by inline assembler in tests gcc.target/i386/cleanup-1.c and gcc.target/i386/cleanup-2.c
- From: "michael.v.zolotukhin at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 23 Jun 2011 11:44:19 +0000
- Subject: [Bug testsuite/49503] Incorrect stack alignment, produced by inline assembler in tests gcc.target/i386/cleanup-1.c and gcc.target/i386/cleanup-2.c
- Auto-submitted: auto-generated
- References: <bug-49503-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49503
--- Comment #5 from Michael Zolotukhin <michael.v.zolotukhin at gmail dot com> 2011-06-23 11:44:17 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > (In reply to comment #0)
> > > >
> > > > As _L_mutex_lock is a function, GCC generates a prologue and epilogue for it -
> > > > in prologue stack alignment is performed (according to ABI64, stack should be
> > > > aligned to 128-bit).
> > >
> > > I didn't see any prologue and epilogue for _L_mutex_lock. Do you have
> > > a run-time testcase to show the problem?
> >
> > I don't have run-time test for this fail, but here is a way to see the problem:
> >
>
> It is very easy to check if stack alignment is correct at run-time.
> Please see how it is done in testcases under gcc.dg/torture/stackalign.
Please find the testcase attached.
It passes on 32 bits and fails on 64 bits (4.7.0 and 4.5.1(RedHat) GCC was
checked).