From: Alan Lawrence <alan.lawrence@arm.com>
To: Richard Biener <rguenther@suse.de>
Cc: Christophe Lyon <christophe.lyon@linaro.org>,
"martin.jambor@suse.cz" <martin.jambor@suse.cz>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jeff Law <law@redhat.com>
Subject: Re: [PATCH 2/5] completely_scalarize arrays as well as records
Date: Fri, 28 Aug 2015 14:05:00 -0000 [thread overview]
Message-ID: <55E0697D.2010008@arm.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1508281500550.4884@zhemvz.fhfr.qr>
Richard Biener wrote:
> On Fri, 28 Aug 2015, Alan Lawrence wrote:
>
>> Christophe Lyon wrote:
>>> I asked because I assumed that Alan saw it pass in his configuration.
>>
>> Bah. No - I now discover a problem in my C++ testsuite setup that was causing
>> a large number of tests to not be executed. I see the problem too now,
>> investigating....
>
> Btw, your patch broke Ada:
>
> +===========================GNAT BUG
> DETECTED==============================+
> | 6.0.0 20150828 (experimental) (x86_64-pc-linux-gnu) GCC error:
> |
> | in completely_scalarize, at tree-sra.c:996
> |
> | Error detected around ../rts/a-coorse.ads:46:24
> |
>
> case ARRAY_TYPE:
> {
> tree elemtype = TREE_TYPE (decl_type);
> tree elem_size = TYPE_SIZE (elemtype);
> gcc_assert (elem_size && tree_fits_uhwi_p (elem_size));
> int el_size = tree_to_uhwi (elem_size);
> gcc_assert (el_size);
>
> tree minidx = TYPE_MIN_VALUE (TYPE_DOMAIN (decl_type));
> tree maxidx = TYPE_MAX_VALUE (TYPE_DOMAIN (decl_type));
> gcc_assert (TREE_CODE (minidx) == INTEGER_CST
> && TREE_CODE (maxidx) == INTEGER_CST);
>
> obviously you missed VLAs. min/max value can also be NULL.
>
> Richard.
>
Right. I think VLA's are the problem with pr64312.C also. I'm testing a fix
(that declares arrays with any of these properties as unscalarizable).
Monday is a bank holiday in UK and so I expect to get back to you on Tuesday.
--Alan
next prev parent reply other threads:[~2015-08-28 14:00 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 11:06 [PATCH 0/5][tree-sra.c] PR/63679 Make SRA replace constant pool loads Alan Lawrence
2015-08-25 11:06 ` [RFC 4/5] Handle constant-pool entries Alan Lawrence
2015-08-25 20:19 ` Jeff Law
2015-08-26 7:24 ` Richard Biener
2015-08-26 15:51 ` Alan Lawrence
2015-08-26 14:08 ` Martin Jambor
2015-08-25 11:06 ` [RFC 5/5] Always completely replace constant pool entries Alan Lawrence
2015-08-25 20:09 ` Jeff Law
2015-08-26 7:29 ` Richard Biener
2015-08-25 11:21 ` [PATCH 2/5] completely_scalarize arrays as well as records Alan Lawrence
2015-08-25 19:40 ` Jeff Law
2015-08-27 16:54 ` Fixing sra-12.c (was: Re: [PATCH 2/5] completely_scalarize arrays as well as records) Alan Lawrence
2015-08-27 20:58 ` Fixing sra-12.c Jeff Law
2015-08-25 21:44 ` [PATCH 2/5] completely_scalarize arrays as well as records Martin Jambor
2015-08-25 21:55 ` Jeff Law
2015-08-26 7:11 ` Richard Biener
2015-08-26 9:39 ` Martin Jambor
2015-08-26 10:12 ` Richard Biener
2015-08-26 16:30 ` Alan Lawrence
2015-08-26 19:18 ` Richard Biener
2015-08-27 16:00 ` Alan Lawrence
2015-08-28 7:19 ` Christophe Lyon
2015-08-28 8:06 ` Richard Biener
2015-08-28 8:16 ` Christophe Lyon
2015-08-28 8:31 ` Richard Biener
2015-08-28 10:09 ` Alan Lawrence
2015-08-28 13:35 ` Richard Biener
2015-08-28 14:05 ` Alan Lawrence [this message]
2015-08-28 15:17 ` Alan Lawrence
2015-09-07 13:20 ` Alan Lawrence
2015-09-08 12:47 ` Martin Jambor
2015-09-14 17:41 ` Alan Lawrence
2015-09-15 7:49 ` Richard Biener
2015-09-17 17:12 ` Alan Lawrence
2015-09-18 8:36 ` Richard Biener
2015-08-25 11:30 ` [PATCH 1/5] Refactor completely_scalarize_var Alan Lawrence
2015-08-25 19:36 ` Jeff Law
2015-08-25 21:42 ` Martin Jambor
2015-08-25 12:30 ` [PATCH 3/5] Build ARRAY_REFs when the base is of ARRAY_TYPE Alan Lawrence
2015-08-25 19:54 ` Jeff Law
2015-08-26 6:34 ` Bin.Cheng
2015-08-26 7:40 ` Richard Biener
2015-08-26 7:41 ` Bin.Cheng
2015-08-26 7:20 ` Richard Biener
2015-08-25 22:51 ` Martin Jambor
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=55E0697D.2010008@arm.com \
--to=alan.lawrence@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=martin.jambor@suse.cz \
--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).