From: "H.J. Lu" <hjl.tools@gmail.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: Richard Henderson <rth@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
richard.sandiford@linaro.org
Subject: Re: Initial shrink-wrapping patch
Date: Thu, 06 Oct 2011 19:25:00 -0000 [thread overview]
Message-ID: <CAMe9rOovO3pyXO4DVmnQZoopFmESC+2aZf4SxWEw9UsaAws2xw@mail.gmail.com> (raw)
In-Reply-To: <4E8DF638.6070907@codesourcery.com>
On Thu, Oct 6, 2011 at 11:40 AM, Bernd Schmidt <bernds@codesourcery.com> wrote:
> On 10/06/11 20:27, H.J. Lu wrote:
>> It also caused:
>>
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50633
>>
>> Don't you need to update ix86_expand_prologue?
>
> In theory it should just work. It seems the x32 stuff has entertaining
> properties :-( Haven't quite figured out how to build it yet, but:
>
> - subq $136, %rsp
> - .cfi_def_cfa_offset 144
> movl $0, %eax
> movl %esp, %ecx
> addl $60, %ecx
> @@ -16,6 +14,8 @@ main:
> movl %eax, (%edx)
> cmpl $16, %eax
> jne .L2
> + subq $136, %rsp
> + .cfi_def_cfa_offset 144
>
> So, this looks like we have both $esp and $rsp - i.e. not using
> stack_pointer_rtx in all cases? Is there a way to avoid this?
X32 has 32bit software stack pointer and 64bit hardware stack
pointer.
> BTW, one other thing that occurred to me - what about drap_reg? Does
> that need to be added to the set of registers whose use requires a prologue?
>
It should be covered by SP.
--
H.J.
next prev parent reply other threads:[~2011-10-06 18:55 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 20:37 Bernd Schmidt
2011-09-01 13:57 ` Richard Sandiford
2011-09-13 2:57 ` Bernd Schmidt
2011-09-13 11:03 ` Richard Sandiford
2011-09-13 12:49 ` Bernd Schmidt
2011-09-13 13:06 ` Richard Sandiford
2011-09-13 13:24 ` Bernd Schmidt
2011-09-13 13:42 ` Richard Sandiford
2011-09-13 17:22 ` Bernd Schmidt
2011-09-15 1:48 ` Richard Henderson
2011-09-27 23:07 ` Bernd Schmidt
2011-09-30 18:19 ` Richard Henderson
2011-10-04 22:19 ` Bernd Schmidt
2011-10-04 22:43 ` Richard Henderson
2011-10-05 15:22 ` Richard Guenther
2011-10-05 16:04 ` Bernd Schmidt
2011-10-05 16:22 ` Richard Henderson
2011-10-05 17:21 ` Bernd Schmidt
2011-10-05 23:35 ` Ian Lance Taylor
2011-10-06 1:43 ` Bernd Schmidt
2011-10-06 6:41 ` Ian Lance Taylor
2011-10-06 10:45 ` Bernd Schmidt
2011-10-06 16:18 ` Ian Lance Taylor
2011-10-06 16:19 ` Bernd Schmidt
2011-10-06 17:32 ` Richard Henderson
2011-10-06 19:39 ` Ian Lance Taylor
2011-10-06 22:15 ` Bernd Schmidt
2011-10-06 22:28 ` Richard Henderson
2011-10-06 13:44 ` Bernd Schmidt
2011-10-06 15:42 ` Richard Henderson
2011-10-06 18:07 ` Bernd Schmidt
2011-10-06 18:19 ` Richard Henderson
2011-10-06 18:28 ` Bernd Schmidt
2011-10-05 17:23 ` Bernd Schmidt
2011-10-05 18:16 ` Richard Henderson
2011-10-06 18:47 ` H.J. Lu
2011-10-06 18:53 ` Bernd Schmidt
2011-10-06 19:25 ` H.J. Lu [this message]
2011-10-03 8:30 ` Richard Sandiford
2011-10-03 11:29 ` Basile Starynkevitch
2011-10-03 16:39 ` Bernd Schmidt
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=CAMe9rOovO3pyXO4DVmnQZoopFmESC+2aZf4SxWEw9UsaAws2xw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@linaro.org \
--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).