From: Eric Botcazou <ebotcazou@adacore.com>
To: gcc-patches@gcc.gnu.org
Subject: [patch v2] Get rid of stack trampolines for nested functions (0/4)
Date: Sun, 04 Sep 2016 20:10:00 -0000 [thread overview]
Message-ID: <1518726.5fkcUnkpqM@arcturus.home> (raw)
Hi,
this is the updated version of the patch initially posted at:
https://gcc.gnu.org/ml/gcc-patches/2016-06/msg02016.html
It takes into account Jeff's remarks, both on the code and the documentation.
As discussed, I'm going to split it into 4 parts: common infrastructure, Ada
front-end bits, individual back-end changes, testsuite. It was bootstrapped
and regtested on x86_64-suse-linux but AdaCore has been using it on native
platforms (Linux, Windows, Solaris, etc) and various architectures (x86,
PowerPC, SPARC, ARM, etc) for years.
ada/gcc-interface/misc.c | 2
ada/gcc-interface/trans.c | 40 +++++++-
builtins.c | 62 +++++++++++++
builtins.def | 2
calls.c | 101 +++++++++++++++++++---
cfgexpand.c | 1
common.opt | 5 +
config/aarch64/aarch64.h | 4
config/alpha/alpha.h | 3
config/arm/arm.c | 27 +++++-
config/arm/arm.h | 4
config/i386/i386.h | 3
config/ia64/ia64.h | 3
config/mips/mips.h | 4
config/pa/pa.h | 3
config/rs6000/rs6000.h | 3
config/sparc/sparc.h | 3
defaults.h | 11 ++
doc/invoke.texi | 24 +++++
doc/tm.texi | 18 ++++
doc/tm.texi.in | 2
gimple.c | 4
gimple.h | 21 ++++
langhooks-def.h | 2
langhooks.h | 4
rtl.h | 5 +
rtlanal.c | 3
target.def | 19 ++++
testsuite/gnat.dg/trampoline3.adb | 22 ++++
testsuite/gnat.dg/trampoline4.adb | 23 +++++
tree-core.h | 9 ++
tree-nested.c | 169 ++++++++++++++++++++++++++++++------
tree.c | 9 +-
tree.h | 10 ++
34 files changed, 574 insertions(+), 51 deletions(-)
--
Eric Botcazou
next reply other threads:[~2016-09-04 20:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 20:10 Eric Botcazou [this message]
2016-09-04 20:12 ` [patch v2] Get rid of stack trampolines for nested functions (1/4) Eric Botcazou
2016-09-12 19:41 ` Jeff Law
2016-09-12 19:45 ` Jeff Law
2016-12-05 20:52 ` Ian Lance Taylor
2016-12-05 21:29 ` Lynn A. Boger
2016-12-05 22:41 ` Ian Lance Taylor
2016-12-05 22:12 ` Eric Botcazou
2016-12-06 17:52 ` Eric Botcazou
2016-12-06 20:18 ` Ian Lance Taylor
2016-12-06 21:59 ` Lynn A. Boger
2016-12-06 22:26 ` Eric Botcazou
2016-12-07 13:38 ` Lynn A. Boger
2016-12-07 13:56 ` Eric Botcazou
2016-12-07 7:23 ` Eric Botcazou
2017-03-23 16:48 ` Andreas Schwab
2017-03-28 17:01 ` Eric Botcazou
2017-03-29 10:05 ` Andreas Schwab
2017-03-29 14:05 ` Eric Botcazou
2017-03-29 14:15 ` Andreas Schwab
2016-09-04 20:14 ` [patch v2] Get rid of stack trampolines for nested functions (2/4) Eric Botcazou
2016-09-04 20:15 ` [patch v2] Get rid of stack trampolines for nested functions (3/4) Eric Botcazou
2016-09-05 10:52 ` Segher Boessenkool
2016-09-12 19:56 ` Jeff Law
2016-09-04 21:31 ` [patch v2] Get rid of stack trampolines for nested functions (4/4) Eric Botcazou
2016-10-16 20:29 ` [patch v2] Get rid of stack trampolines for nested functions (0/4) Eric Botcazou
2016-10-17 10:40 ` Andreas Schwab
2016-10-17 11:14 ` Eric Botcazou
2016-10-17 22:35 ` Eric Botcazou
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=1518726.5fkcUnkpqM@arcturus.home \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@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).