From: Mike Stump <mikestump@comcast.net>
To: Michael Matz <matz@suse.de>
Cc: Jason Merrill <jason@redhat.com>,
Richard Guenther <richard.guenther@gmail.com>,
Xinliang David Li <davidxl@google.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: New option to turn off stack reuse for temporaries
Date: Tue, 26 Jun 2012 20:12:00 -0000 [thread overview]
Message-ID: <E56E4DCF-27F5-46E3-AA67-113A02165E0F@comcast.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1206261802510.25982@wotan.suse.de>
On Jun 26, 2012, at 9:07 AM, Michael Matz wrote:
> I agree with Jason. TARGET_EXPR and CLEANUP_POINT_EXPR might currently be
> used only for C++, but I think they are sensible general constructs to be
> supported by the gimplifier.
As do I. The intent was for Ada and every other language with things like temporaries and cleanups to reuse the backend constructs, so that instead of writing optimizers, one for each language, to instead share the optimizer across languages. To me, the middle end and the backend are the best places for these.
next prev parent reply other threads:[~2012-06-26 20:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 23:44 Xinliang David Li
2012-06-21 5:28 ` Jason Merrill
2012-06-21 6:06 ` Xinliang David Li
2012-06-21 6:27 ` Jason Merrill
2012-06-21 9:32 ` Richard Guenther
2012-06-21 16:41 ` Michael Matz
2012-06-22 8:46 ` Richard Guenther
2012-06-21 18:19 ` Jason Merrill
2012-06-21 18:44 ` Xinliang David Li
2012-06-22 8:50 ` Richard Guenther
2012-06-22 9:39 ` Jason Merrill
2012-06-22 9:51 ` Richard Guenther
2012-06-22 16:09 ` Xinliang David Li
2012-06-25 16:29 ` Xinliang David Li
2012-06-26 8:42 ` Richard Guenther
2012-06-26 15:29 ` Jason Merrill
2012-06-26 17:12 ` Michael Matz
2012-06-26 17:19 ` Jakub Jelinek
2012-06-26 20:12 ` Mike Stump [this message]
2012-06-27 3:03 ` Eric Botcazou
2012-06-29 8:18 ` Xinliang David Li
2012-07-02 23:30 ` Xinliang David Li
2012-07-04 15:01 ` Xinliang David Li
2012-07-09 16:31 ` Xinliang David Li
2012-07-09 22:53 ` Jason Merrill
2012-12-02 12:32 ` Olivier Ballereau
2012-12-03 1:03 ` Xinliang David Li
2012-06-22 21:09 Jason Merrill
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=E56E4DCF-27F5-46E3-AA67-113A02165E0F@comcast.net \
--to=mikestump@comcast.net \
--cc=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=matz@suse.de \
--cc=richard.guenther@gmail.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).