public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	 gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Put front-end temporaries into BLOCKs
Date: Tue, 26 Apr 2011 01:23:00 -0000	[thread overview]
Message-ID: <4DB5F88C.5060309@netcologne.de> (raw)
In-Reply-To: <4DB2EED0.8050708@netcologne.de>

Am 23.04.2011 17:22, schrieb Thomas Koenig:
> Hello world,
>
> the attached patch puts temporary variables, and the statement they are
> being generated for, in their own BLOCK.
>
> This may or may not be useful for data locality, and for telling the
> middle end explicitly about the lifetime of the temporary variables. It
> is intended as a step towards eliminating redundant calls to
> array-valued functions whose bounds are unknown at compile time, such as
> the original test case for PR 22572.
>
> No test case, as this should not change anything.
>
> Regression-tested. OK for trunk?
>

Ping ** 0.25?

	Thomas

  reply	other threads:[~2011-04-25 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23 20:12 Thomas Koenig
2011-04-26  1:23 ` Thomas Koenig [this message]
2011-04-26  4:58 ` Jerry DeLisle
2011-04-26 21:14   ` Thomas Koenig

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=4DB5F88C.5060309@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=fortran@gcc.gnu.org \
    --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).