From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org, ebotcazou@adacore.com
Subject: Re: [PATCH] Use ECF_MAY_BE_ALLOCA for __builtin_alloca_with_align (PR tree-optimization/68680)
Date: Fri, 04 Dec 2015 10:50:00 -0000 [thread overview]
Message-ID: <20151204104715.GL5675@tucnak.redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1512041021120.4884@t29.fhfr.qr>
On Fri, Dec 04, 2015 at 10:30:38AM +0100, Richard Biener wrote:
> > The following patch has been bootstrapped/regtested on x86_64-linux and
> > i686-linux.
>
> The patch is ok - it looks like you could have removed the
> __builtin_alloca strcmp with it though.
Ok, will remove the strcmp then.
> Does the patch mean we inlined __builtin_alloca_with_align ()
> functions? We might run into the issue Eric fixed lately with
Yes, see testcase below. 4.7+ inlines it. As for tail call optimization,
seems we are just lucky there (f4), as fab pass which is quite late
turns the __builtin_stack_restore into GIMPLE_NOP and tailc pass does not
ignore nops. Shall I commit following patch to trunk to fix that up
(after committing this VLA fix of course)?
int f1 (char *);
static inline void
f2 (int x)
{
char a[x];
f1 (a);
}
void
f3 (int x)
{
f2 (x);
f2 (x);
f2 (x);
f2 (x);
}
int
f4 (int x)
{
char a[x];
return f1 (a);
}
2015-12-04 Jakub Jelinek <jakub@redhat.com>
* tree-tailcall.c (find_tail_calls): Ignore GIMPLE_NOPs.
--- gcc/tree-tailcall.c.jj 2015-11-04 11:12:17.000000000 +0100
+++ gcc/tree-tailcall.c 2015-12-04 11:43:01.296110941 +0100
@@ -412,9 +412,10 @@ find_tail_calls (basic_block bb, struct
{
stmt = gsi_stmt (gsi);
- /* Ignore labels, returns, clobbers and debug stmts. */
+ /* Ignore labels, returns, nops, clobbers and debug stmts. */
if (gimple_code (stmt) == GIMPLE_LABEL
|| gimple_code (stmt) == GIMPLE_RETURN
+ || gimple_code (stmt) == GIMPLE_NOP
|| gimple_clobber_p (stmt)
|| is_gimple_debug (stmt))
continue;
@@ -532,7 +533,8 @@ find_tail_calls (basic_block bb, struct
stmt = gsi_stmt (agsi);
- if (gimple_code (stmt) == GIMPLE_LABEL)
+ if (gimple_code (stmt) == GIMPLE_LABEL
+ || gimple_code (stmt) == GIMPLE_NOP)
continue;
if (gimple_code (stmt) == GIMPLE_RETURN)
Jakub
next prev parent reply other threads:[~2015-12-04 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 22:43 Jakub Jelinek
2015-12-04 9:30 ` Richard Biener
2015-12-04 10:18 ` Eric Botcazou
2015-12-04 10:50 ` Jakub Jelinek [this message]
2015-12-04 11:00 ` Richard Biener
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=20151204104715.GL5675@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).