From: Jeff Law <law@redhat.com>
To: vogt@linux.vnet.ibm.com, gcc-patches@gcc.gnu.org,
Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2][v4] Drop excess size used for run time allocated stack variables.
Date: Thu, 18 Aug 2016 16:20:00 -0000 [thread overview]
Message-ID: <ffa873c3-416e-cbb8-c444-9d9494478cc0@redhat.com> (raw)
In-Reply-To: <20160726155317.GA5718@linux.vnet.ibm.com>
On 07/26/2016 09:53 AM, Dominik Vogt wrote:
> Finally a patch that works and is simple. Bootstrapped and
> regression tested on s390, s390x biarch and x86_64. The new patch
> exploits the known alignment of (stack pointer +
> STACK_DYNAMIC_OFFSET) as described earlier (see below). I think
> that is the right way to get rid of the extra allocation. It
> took a long time to understand the problem.
>
> As the patch triggers a bug in the fortran compiler, the
> der_type.f90 test case may fail on some targets if this patch is
> used without the fortran fix that I've posted in another thread.
>
> (The patch also contains a fix for a typo in a comment in the
> patched function.)
>
> See ChangeLog for a full description of the new patch.
>
> Since the patch is all new, we're not going to commit it without a
> new OK.
I like this one much better :-)
OK.
Thanks for your patience,
JEff
next prev parent reply other threads:[~2016-08-18 16:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 22:13 [PATCH] " Dominik Vogt
2016-04-29 22:15 ` Dominik Vogt
2016-04-30 9:44 ` Eric Botcazou
2016-04-30 10:14 ` Dominik Vogt
2016-05-02 13:43 ` Dominik Vogt
2016-05-02 15:10 ` Jeff Law
2016-05-03 14:18 ` Dominik Vogt
2016-05-19 23:11 ` Jeff Law
2016-05-20 21:24 ` [RFA] Minor cleanup to allocate_dynamic_stack_space Jeff Law
2016-05-20 21:44 ` Eric Botcazou
2016-05-20 21:48 ` Jeff Law
2016-05-23 7:53 ` Eric Botcazou
2016-05-23 10:12 ` Dominik Vogt
2016-05-25 12:46 ` Dominik Vogt
2016-06-09 12:00 ` [PATCH] Drop excess size used for run time allocated stack variables Bernd Schmidt
2016-06-21 9:35 ` Dominik Vogt
2016-06-21 22:26 ` Jeff Law
2016-06-22 8:57 ` Dominik Vogt
2016-05-25 14:02 ` [PATCH 1/2][v3] " Dominik Vogt
2016-05-25 14:31 ` [PATCH 2/2][v3] " Dominik Vogt
2016-05-25 14:51 ` Dominik Vogt
2016-06-08 11:21 ` Bernd Schmidt
2016-06-20 12:20 ` Dominik Vogt
2016-06-20 12:20 ` Bernd Schmidt
2016-06-23 4:24 ` Jeff Law
2016-06-23 9:57 ` Dominik Vogt
2016-07-21 20:07 ` Jeff Law
2016-07-22 12:02 ` Dominik Vogt
2016-07-26 15:53 ` [PATCH 2/2][v4] " Dominik Vogt
2016-08-18 16:20 ` Jeff Law [this message]
2016-08-23 9:23 ` Andreas Krebbel
2016-06-08 11:20 ` [PATCH 1/2][v3] " Bernd Schmidt
2016-06-08 12:20 ` Eric Botcazou
2016-06-22 20:34 ` Jeff Law
2016-07-04 14:22 ` Andreas Krebbel
2016-08-24 2:02 [PATCH 2/2][v4] " David Edelsohn
2016-08-24 11:42 ` Andreas Krebbel
2016-08-24 12:57 ` David Edelsohn
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=ffa873c3-416e-cbb8-c444-9d9494478cc0@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=krebbel@linux.vnet.ibm.com \
--cc=vogt@linux.vnet.ibm.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).