public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39118] [4.3/4.4 Regression] x86_64 red zone violation
Date: Wed, 11 Feb 2009 11:43:00 -0000 [thread overview]
Message-ID: <20090211114340.22671.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39118-1313@http.gcc.gnu.org/bugzilla/>
------- Comment #19 from uros at gcc dot gnu dot org 2009-02-11 11:43 -------
Subject: Bug 39118
Author: uros
Date: Wed Feb 11 11:43:24 2009
New Revision: 144100
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=144100
Log:
PR target/39118
* config/i386/i386.md (UNSPEC_MEMORY_BLOCKAGE): New constant.
(memory_blockage): New expander.
(*memory_blockage): New insn pattern.
* config/i386/i386.c (ix86_expand_prologue): Use memory_blockage
instead of general blockage at the end of function prologue when
frame pointer is used to access red zone area. Do not emit blockage
when profiling, it is emitted in generic code.
(ix86_expand_epilogue): Emit memory_blockage at the beginning of
function epilogue when frame pointer is used to access red zone area.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.c
trunk/gcc/config/i386/i386.md
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39118
next prev parent reply other threads:[~2009-02-11 11:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 5:52 [Bug target/39118] New: " ian at airs dot com
2009-02-06 5:53 ` [Bug target/39118] " ian at airs dot com
2009-02-06 13:45 ` ubizjak at gmail dot com
2009-02-06 14:14 ` ian at airs dot com
2009-02-06 14:50 ` ubizjak at gmail dot com
2009-02-06 15:05 ` ubizjak at gmail dot com
2009-02-06 16:44 ` hjl dot tools at gmail dot com
2009-02-06 17:25 ` ian at airs dot com
2009-02-08 21:01 ` [Bug target/39118] [4.3/4.4 Regression] " ubizjak at gmail dot com
2009-02-09 21:22 ` jsm28 at gcc dot gnu dot org
2009-02-10 16:13 ` uros at gcc dot gnu dot org
2009-02-10 16:13 ` uros at gcc dot gnu dot org
2009-02-10 16:14 ` ubizjak at gmail dot com
2009-02-10 19:56 ` ian at airs dot com
2009-02-10 21:04 ` ian at airs dot com
2009-02-10 21:11 ` ian at airs dot com
2009-02-11 7:09 ` ubizjak at gmail dot com
2009-02-11 8:24 ` ubizjak at gmail dot com
2009-02-11 8:32 ` ubizjak at gmail dot com
2009-02-11 11:00 ` jakub at gcc dot gnu dot org
2009-02-11 11:43 ` uros at gcc dot gnu dot org [this message]
2009-02-11 11:54 ` uros at gcc dot gnu dot org
2009-02-11 11:55 ` ubizjak at gmail dot com
2009-02-11 14:49 ` ian at airs dot com
2009-02-17 18:40 ` rguenth at gcc dot gnu dot org
2009-02-17 18:45 ` hjl dot tools at gmail dot com
2009-02-17 19:00 ` rguenther at suse dot de
2009-02-17 19:50 ` rguenther at suse dot de
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=20090211114340.22671.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).