From: "Jiangning Liu" <jiangning.liu@arm.com>
To: "'Jakub Jelinek'" <jakub@redhat.com>
Cc: "'Joern Rennecke'" <amylaar@spamcop.net>, <gcc@gcc.gnu.org>,
<gcc-patches@gcc.gnu.org>, <vmakarov@redhat.com>,
<dje.gcc@gmail.com>, "Richard Henderson" <rth@redhat.com>,
"Ramana Radhakrishnan" <Ramana.Radhakrishnan@arm.com>,
"'Ramana Radhakrishnan'" <ramana.radhakrishnan@linaro.org>
Subject: RE: [RFC] Add middle end hook for stack red zone size
Date: Mon, 01 Aug 2011 10:15:00 -0000 [thread overview]
Message-ID: <000a01cc5033$cf0817b0$6d184710$@liu@arm.com> (raw)
In-Reply-To: <20110801091151.GD27949@sunsite.ms.mff.cuni.cz>
The answer is ARM can. However, if you look into the bugs PR30282 and
PR38644, PR44199, you may find in history, there are several different cases
in different ports reporting the similar failures, covering x86, PowerPC and
ARM. You are right, they were all fixed in back-ends in the past, but we
should
fix the bug in a general way to make GCC infrastructure stronger, rather
than fixing the problem target-by-target and case-by-case! If you further
look into the back-end fixes in x86 and PowerPC, you may find they looks
quite similar in back-ends.
Thanks,
-Jiangning
> -----Original Message-----
> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-owner@gcc.gnu.org]
> On Behalf Of Jakub Jelinek
> Sent: Monday, August 01, 2011 5:12 PM
> To: Jiangning Liu
> Cc: 'Joern Rennecke'; gcc@gcc.gnu.org; gcc-patches@gcc.gnu.org;
> vmakarov@redhat.com; dje.gcc@gmail.com; Richard Henderson; Ramana
> Radhakrishnan; 'Ramana Radhakrishnan'
> Subject: Re: [RFC] Add middle end hook for stack red zone size
>
> On Mon, Aug 01, 2011 at 11:44:04AM +0800, Jiangning Liu wrote:
> > It's quite necessary to solve the general problem in middle-end rather
than in
> back-end.
>
> That's what we disagree on. All back-ends but ARM are able to handle it
> right, why can't ARM too? The ABI rules for stack handling in the
epilogues
> are simply too diverse and complex to be handled easily in the scheduler.
>
> Jakub
next prev parent reply other threads:[~2011-08-01 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4e255312.0a852b0a.528d.6933SMTPIN_ADDED@mx.google.com>
[not found] ` <CACUk7=WsaUN+TUw7rb8-o1EukoaCMrAh8bFJM6832LtRmfkofg@mail.gmail.com>
2011-07-26 1:31 ` Jiangning Liu
2011-07-26 11:25 ` Joern Rennecke
2011-08-01 3:44 ` Jiangning Liu
2011-08-01 9:12 ` Jakub Jelinek
2011-08-01 10:03 ` Joseph S. Myers
2011-08-01 10:15 ` Jiangning Liu [this message]
2011-08-01 10:31 ` Jakub Jelinek
2011-08-02 4:46 ` Jiangning Liu
2011-08-01 10:16 ` Richard Earnshaw
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='000a01cc5033$cf0817b0$6d184710$@liu@arm.com' \
--to=jiangning.liu@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=amylaar@spamcop.net \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=ramana.radhakrishnan@linaro.org \
--cc=rth@redhat.com \
--cc=vmakarov@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).