From: NightStrike <nightstrike@gmail.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Henderson <rth@redhat.com>
Subject: Re: [RFA patch i386]: Prepare x64 prologue using positive offsets for frame-pointer
Date: Wed, 14 Jul 2010 19:29:00 -0000 [thread overview]
Message-ID: <AANLkTinW3q5_xjy6j-MjVUtlcMoeG0qKeoH6PiWJUhJ0@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinQW8cn9uoJO7omzuyLuz1IHgEptTEZFnZGRUoh@mail.gmail.com>
On Mon, Jul 5, 2010 at 2:17 AM, Kai Tietz <ktietz70@googlemail.com> wrote:
> 2010/7/4 Kai Tietz <ktietz70@googlemail.com>:
>> Hello,
>>
>> this patch prepares for x64 SEH, that frame-pointer points at end of
>> stack-prologue. This is required for x64, because the SEH unwind
>> information can't express negative offsets for stack.
>>
>> ChangeLog
>>
>> 2010-07-04 Kai Tietz
>>
>> * config/i386/i386.c (ix86_compute_frame_layout): Let frame's
>> hard_frame_pointer_offset point to end of prologue.
>> (ix86_expand_prologue): Handle x64 frame-pointer prologue.
>> (ix86_expand_epilogue): Handle x64 frame-pointer epilogue.
>>
>> Tested for i686-pc-cygwin, x86_64-pc-mingw32. Ok for apply?
>>
>> Regards,
>> Kai
>
> This update patch avoids, that for profiling-built the x64
> frame-layout gets used. It would lead to issues, caused by profiling
> code, which assumes old stack-frame layout.
>
> Regards,
> Kai
>
>
> --
> | (\_/) This is Bunny. Copy and paste
> | (='.'=) Bunny into your signature to help
> | (")_(") him gain world domination
>
Ping
next prev parent reply other threads:[~2010-07-14 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 21:06 Kai Tietz
2010-07-05 6:18 ` Kai Tietz
2010-07-14 19:29 ` NightStrike [this message]
2010-07-18 10:42 ` Kai Tietz
2010-07-20 22:57 ` Richard Henderson
2010-07-21 7:43 ` Kai Tietz
2010-07-21 17:36 ` Richard Henderson
2010-07-21 18:06 ` Kai Tietz
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=AANLkTinW3q5_xjy6j-MjVUtlcMoeG0qKeoH6PiWJUhJ0@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.com \
--cc=rth@redhat.com \
/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).