From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: James Greenhalgh <James.Greenhalgh@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>,
Jiong Wang <Jiong.Wang@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
"Marcus Shawcroft" <Marcus.Shawcroft@arm.com>
Subject: Re: [RFC][PATCH][AArch64] Cleanup frame pointer usage
Date: Wed, 14 Jun 2017 15:49:00 -0000 [thread overview]
Message-ID: <AM5PR0802MB2610525C80EBE9CBECC5AE9983C30@AM5PR0802MB2610.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20170614145109.GF8010@arm.com>
James Greenhalgh wrote:
> I note this is still marked as an RFC, are you now proposing it as a
> patch to be merged to trunk?
Absolutely. It was marked as an RFC to get some comments - I thought it
may be controversial to separate the frame pointer and frame chain concept.
And this fixes the long standing bugs caused by changing the global frame
pointer option to an incorrect value for the leaf function optimization.
Wilco
next prev parent reply other threads:[~2017-06-14 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 18:29 Wilco Dijkstra
2016-11-14 13:09 ` Wilco Dijkstra
2016-12-06 15:06 ` Wilco Dijkstra
2016-12-14 16:42 ` Wilco Dijkstra
2017-01-17 12:11 ` Wilco Dijkstra
2017-04-20 16:43 ` Wilco Dijkstra
2017-06-13 13:59 ` Wilco Dijkstra
2017-06-14 14:51 ` James Greenhalgh
2017-06-14 15:49 ` Wilco Dijkstra [this message]
2017-06-15 14:12 ` Wilco Dijkstra
2017-06-15 15:39 ` Jiong Wang
2017-06-15 17:43 ` Wilco Dijkstra
2017-06-27 15:37 ` Wilco Dijkstra
2017-07-14 14:30 ` Wilco Dijkstra
2017-07-21 11:23 ` Wilco Dijkstra
2017-08-01 10:19 ` Wilco Dijkstra
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=AM5PR0802MB2610525C80EBE9CBECC5AE9983C30@AM5PR0802MB2610.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=Jiong.Wang@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.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).