From: Richard Biener <richard.guenther@gmail.com>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Don't treat variable-length vectors as VLAs during gimplification
Date: Wed, 18 Sep 2019 08:56:00 -0000 [thread overview]
Message-ID: <CAFiYyc17=zAC9C=D8K9eFKbANDcU53MSx7t8==eMoOhLLy9fOg@mail.gmail.com> (raw)
In-Reply-To: <mptwoe614f7.fsf@arm.com>
On Wed, Sep 18, 2019 at 8:53 AM Richard Sandiford
<richard.sandiford@arm.com> wrote:
>
> Source-level SVE vectors should be gimplified in the same way
> as normal fixed-length vectors rather than as VLAs.
>
> This is tested by later SVE patches.
>
> Tested on aarch64-linux-gnu with SVE (with and without follow-on
> patches) and x86_64-linux-gnu. OK to install?
OK.
Richard.
> Richard
>
>
> 2019-09-18 Richard Sandiford <richard.sandiford@arm.com>
>
> gcc/
> * gimplify.c (gimplify_decl_expr): Use poly_int_tree_p instead
> of checking specifically for INTEGER_CST.
>
> Index: gcc/gimplify.c
> ===================================================================
> --- gcc/gimplify.c 2019-08-08 18:11:51.411313290 +0100
> +++ gcc/gimplify.c 2019-09-18 07:52:22.799034800 +0100
> @@ -1754,11 +1754,12 @@ gimplify_decl_expr (tree *stmt_p, gimple
> tree init = DECL_INITIAL (decl);
> bool is_vla = false;
>
> - if (TREE_CODE (DECL_SIZE_UNIT (decl)) != INTEGER_CST
> + poly_uint64 size;
> + if (!poly_int_tree_p (DECL_SIZE_UNIT (decl), &size)
> || (!TREE_STATIC (decl)
> && flag_stack_check == GENERIC_STACK_CHECK
> - && compare_tree_int (DECL_SIZE_UNIT (decl),
> - STACK_CHECK_MAX_VAR_SIZE) > 0))
> + && maybe_gt (size,
> + (unsigned HOST_WIDE_INT) STACK_CHECK_MAX_VAR_SIZE)))
> {
> gimplify_vla_decl (decl, seq_p);
> is_vla = true;
prev parent reply other threads:[~2019-09-18 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 6:53 Richard Sandiford
2019-09-18 8:56 ` Richard Biener [this message]
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='CAFiYyc17=zAC9C=D8K9eFKbANDcU53MSx7t8==eMoOhLLy9fOg@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).