public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/42313] FAIL: gcc.target/i386/builtin-unreachable.c scan-assembler-not %e[bs]p on i686 darwin
Date: Tue, 08 Dec 2009 19:51:00 -0000 [thread overview]
Message-ID: <20091208195120.19727.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42313-11113@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from pinskia at gcc dot gnu dot org 2009-12-08 19:51 -------
I think this comes down to an alignment issue. On darwin, the stack has to be
aligned to 16bytes so something inside i386.c is deciding that we to allocate
the stack frame as there was something on the stack and we have to align it
again.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu dot
| |org
Component|testsuite |target
GCC build triplet|i686-apple-darwin* |
GCC host triplet|i686-apple-darwin* |
GCC target triplet|i686-apple-darwin* |i?86-apple-darwin*
Keywords| |missed-optimization
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42313
next prev parent reply other threads:[~2009-12-08 19:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 20:11 [Bug testsuite/42313] New: " howarth at nitro dot med dot uc dot edu
2009-12-06 20:12 ` [Bug testsuite/42313] " howarth at nitro dot med dot uc dot edu
2009-12-06 20:13 ` howarth at nitro dot med dot uc dot edu
2009-12-07 17:27 ` daney at gcc dot gnu dot org
2009-12-08 14:13 ` howarth at nitro dot med dot uc dot edu
2009-12-08 17:34 ` daney at gcc dot gnu dot org
2009-12-08 19:51 ` pinskia at gcc dot gnu dot org [this message]
2010-03-03 16:56 ` [Bug target/42313] " mikestump at comcast dot net
2010-09-04 19:13 ` howarth at nitro dot med dot uc dot edu
2010-09-04 21:20 ` howarth at nitro dot med dot uc dot edu
2010-09-07 21:19 ` hjl at gcc dot gnu dot org
2010-09-08 1:05 ` howarth at nitro dot med dot uc dot edu
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=20091208195120.19727.qmail@sourceware.org \
--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).