From: Christophe Lyon <christophe.lyon@linaro.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Richard Biener <rguenther@suse.de>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] More compile-time saving in BB vectorization
Date: Fri, 13 Nov 2015 08:31:00 -0000 [thread overview]
Message-ID: <CAKdteObrwmPgnDwd75vkXdPDsEdKurg4k1bo1WAbOjbg+cWkKA@mail.gmail.com> (raw)
In-Reply-To: <CAKdteObA1Tgxt8LhB0GZEV-15dy+00sAg6QVOJQrbgCjWh4mLQ@mail.gmail.com>
On 12 November 2015 at 21:04, Christophe Lyon
<christophe.lyon@linaro.org> wrote:
> On 12 November 2015 at 16:49, Andreas Schwab <schwab@suse.de> wrote:
>> Richard Biener <rguenther@suse.de> writes:
>>
>>> * tree-vectorizer.h (vect_slp_analyze_and_verify_instance_alignment):
>>> Declare.
>>> (vect_analyze_data_refs_alignment): Make loop vect specific.
>>> (vect_verify_datarefs_alignment): Likewise.
>>> * tree-vect-data-refs.c (vect_slp_analyze_data_ref_dependences):
>>> Add missing continue.
>>> (vect_compute_data_ref_alignment): Export.
>>> (vect_compute_data_refs_alignment): Merge into...
>>> (vect_analyze_data_refs_alignment): ... this.
>>> (verify_data_ref_alignment): Split out from ...
>>> (vect_verify_datarefs_alignment): ... here.
>>> (vect_slp_analyze_and_verify_node_alignment): New function.
>>> (vect_slp_analyze_and_verify_instance_alignment): Likewise.
>>> * tree-vect-slp.c (vect_supported_load_permutation_p): Remove
>>> misplaced checks on alignment.
>>> (vect_slp_analyze_bb_1): Add fatal output parameter. Do
>>> alignment analysis after SLP discovery and do it per instance.
>>> (vect_slp_bb): When vect_slp_analyze_bb_1 fatally failed do not
>>> bother to re-try using different vector sizes.
>>
>> This breaks libgfortran on ia64:
>>
>> ../../../libgfortran/generated/matmul_c4.c: In function 'matmul_c4':
>> ../../../libgfortran/generated/matmul_c4.c:79:1: internal compiler error: in vectorizable_store, at tree-vect-stmts.c:5651
>> matmul_c4 (gfc_array_c4 * const restrict retarray,
>> ^
>> 0x40000000010ff01f vectorizable_store
>> ../../gcc/tree-vect-stmts.c:5651
>> 0x4000000001115b5f vect_transform_stmt(gimple*, gimple_stmt_iterator*, bool*, _slp_tree*, _slp_instance*)
>> ../../gcc/tree-vect-stmts.c:8003
>> 0x400000000114df1f vect_schedule_slp_instance
>> ../../gcc/tree-vect-slp.c:3484
>> 0x4000000001154d6f vect_schedule_slp(vec_info*)
>> ../../gcc/tree-vect-slp.c:3549
>> 0x40000000011562bf vect_slp_bb(basic_block_def*)
>> ../../gcc/tree-vect-slp.c:2543
>> 0x4000000001159f2f execute
>> ../../gcc/tree-vectorizer.c:734
>>
>
> Same problem on armeb.
>
Now fixed at r230260 (pr68308).
Thanks.
>
>> Andreas.
>>
>> --
>> Andreas Schwab, SUSE Labs, schwab@suse.de
>> GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
>> "And now for something completely different."
prev parent reply other threads:[~2015-11-13 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 14:29 Richard Biener
2015-11-12 15:49 ` Andreas Schwab
2015-11-12 20:04 ` Christophe Lyon
2015-11-13 8:31 ` Christophe Lyon [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=CAKdteObrwmPgnDwd75vkXdPDsEdKurg4k1bo1WAbOjbg+cWkKA@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=schwab@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).