public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/98155] New: [11 Regression] ICE during GIMPLE pass: slp, in vect_init_pattern_stmt
Date: Sat, 05 Dec 2020 14:52:39 +0000	[thread overview]
Message-ID: <bug-98155-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98155

            Bug ID: 98155
           Summary: [11 Regression] ICE during GIMPLE pass: slp, in
                    vect_init_pattern_stmt
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: doko at debian dot org
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

seen with profiled-bootstrap + LTO enabled build, at least on x86_64-linux-gnu
and s390x-linux-gnu:

during GIMPLE pass: slp
../../src/gcc/ada/bindo-graphs.adb: In function
'bindo__graphs__library_graphs__is_spec_with_elaborate_body':
../../src/gcc/ada/bindo-graphs.adb:3469:7: internal compiler error: in
vect_init_pattern_stmt, at tree-vect-patterns.c:115
 3469 |       function Is_Spec_With_Elaborate_Body
      |       ^
0x94821e vect_init_pattern_stmt
        ../../src/gcc/tree-vect-patterns.c:115
0x1a51783 vect_set_pattern_stmt
        ../../src/gcc/tree-vect-patterns.c:133
0x1a51783 vect_mark_pattern_stmts
        ../../src/gcc/tree-vect-patterns.c:5352
0x1a51783 vect_pattern_recog_1
        ../../src/gcc/tree-vect-patterns.c:5468
0x1a60ae1 vect_pattern_recog(vec_info*)
        ../../src/gcc/tree-vect-patterns.c:5608
0x94821e vect_init_pattern_stmt
        ../../src/gcc/tree-vect-patterns.c:115
0x1a51783 vect_set_pattern_stmt
        ../../src/gcc/tree-vect-patterns.c:133
0x1a51783 vect_mark_pattern_stmts
        ../../src/gcc/tree-vect-patterns.c:5352
0x1a51783 vect_pattern_recog_1
        ../../src/gcc/tree-vect-patterns.c:5468
0x1a60ae1 vect_pattern_recog(vec_info*)
        ../../src/gcc/tree-vect-patterns.c:5608
0x11443e2 vect_slp_analyze_bb_1
        ../../src/gcc/tree-vect-slp.c:4242
0x11443e2 vect_slp_region
        ../../src/gcc/tree-vect-slp.c:4347
0x1145de7 vect_slp_bbs
        ../../src/gcc/tree-vect-slp.c:4495
0x11461f4 vect_slp_function(function*)
        ../../src/gcc/tree-vect-slp.c:4581
0x1147b32 execute
        ../../src/gcc/tree-vectorizer.c:1436
Please submit a full bug report,
with preprocessed source if appropriate.

s390x:
during GIMPLE pass: slp
../../src/gcc/ada/bindo-augmentors.adb: In function
'bindo__augmentors__library_graph_augmentors__visit_vertex':
../../src/gcc/ada/bindo-augmentors.adb:206:7: internal compiler error: in
vect_init_pattern_stmt, at tree-vect-patterns.c:115
  206 |       procedure Visit_Vertex
      |       ^
0x23b330f vect_init_pattern_stmt
        ../../src/gcc/tree-vect-patterns.c:115
0x23b3739 vect_set_pattern_stmt
        ../../src/gcc/tree-vect-patterns.c:133
0x23b3739 vect_mark_pattern_stmts
        ../../src/gcc/tree-vect-patterns.c:5352
0x23b3739 vect_pattern_recog_1
        ../../src/gcc/tree-vect-patterns.c:5468
0x23c5fa3 vect_pattern_recog(vec_info*)
        ../../src/gcc/tree-vect-patterns.c:5608
0x1bafd87 vect_slp_analyze_bb_1
        ../../src/gcc/tree-vect-slp.c:4242
0x1bafd87 vect_slp_region
        ../../src/gcc/tree-vect-slp.c:4347
0x1bb1863 vect_slp_bbs
        ../../src/gcc/tree-vect-slp.c:4495
0x1bb1cf5 vect_slp_function(function*)
        ../../src/gcc/tree-vect-slp.c:4581
0x1bb3867 execute
        ../../src/gcc/tree-vectorizer.c:1436
Please submit a full bug report,
with preprocessed source if appropriate.

GCC configured with:

         --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++
         --prefix=/usr/lib/gcc-snapshot
         --with-gcc-major-version-only
         --program-prefix=
         --enable-shared
         --enable-linker-build-id
         --disable-nls
         --enable-bootstrap
         --enable-clocale=gnu
         --enable-libstdcxx-debug
         --enable-libstdcxx-time=yes
         --with-default-libstdcxx-abi=new
         --enable-gnu-unique-object
         --disable-vtable-verify
         --enable-plugin
         --with-system-zlib
         --enable-libphobos-checking=release
         --with-target-system-zlib=auto
         --enable-objc-gc=auto
         --enable-multiarch
         --disable-werror
         --enable-cet
         --with-arch-32=i686
         --with-abi=m64
         --with-multilib-list=m32,m64,mx32
         --enable-multilib
         --with-tune=generic
         --without-cuda-driver
         --enable-checking=yes,extra,rtl
         --build=x86_64-linux-gnu
         --host=x86_64-linux-gnu
         --target=x86_64-linux-gnu
         --with-build-config=bootstrap-lto-lean
         --enable-link-serialization=2

             reply	other threads:[~2020-12-05 14:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 14:52 doko at debian dot org [this message]
2020-12-06  9:35 ` [Bug lto/98155] " marxin at gcc dot gnu.org
2020-12-06  9:53 ` doko at debian dot org
2020-12-06 10:22 ` doko at debian dot org
2020-12-06 14:51 ` marxin at gcc dot gnu.org
2020-12-07  7:54 ` [Bug tree-optimization/98155] " rguenth at gcc dot gnu.org
2020-12-07  7:55 ` rguenth at gcc dot gnu.org
2020-12-07 10:05 ` marxin at gcc dot gnu.org

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=bug-98155-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).