public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96448] New: ICE: maximum number of generated reload insns per insn achieved (90) Date: Tue, 04 Aug 2020 03:15:17 +0000 [thread overview] Message-ID: <bug-96448-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96448 Bug ID: 96448 Summary: ICE: maximum number of generated reload insns per insn achieved (90) Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- Target: powerpc-*-linux-gnu Probably another invalid target issue, but still… gcc-11.0.0-alpha20200802 snapshot (g:6e46b3f3da5c03bc529b3690dd0995927feb9142) configured for a 32-bit BE powerpc target ICEs when compiling the following testcase, extracted from test/CodeGen/x86-inline-asm-min-vector-width.c from clang 10.0.1 test suite, w/ -mcpu=power10: typedef long long __m256i __attribute__ ((vector_size (32))); __m256i testYMMout(__m256i *p) { __m256i ymm0; __asm__("vmovdqu %1, %0" :"=v"(ymm0) : "m"(*(__m256i*)p)); return ymm0; } % powerpc-e300c3-linux-gnu-gcc-11.0.0 -mcpu=power10 -w -c dcbvmywg.c dcbvmywg.c: In function 'testYMMout': dcbvmywg.c:5:3: note: the layout of aggregates containing vectors with 32-byte alignment has changed in GCC 5 5 | __asm__("vmovdqu %1, %0" :"=v"(ymm0) : "m"(*(__m256i*)p)); | ^~~~~~~ during RTL pass: reload dcbvmywg.c:7:1: internal compiler error: maximum number of generated reload insns per insn achieved (90) 7 | } | ^ 0xc1ddd0 lra_constraints(bool) /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200802/work/gcc-11-20200802/gcc/lra-constraints.c:4954 0xc07540 lra(_IO_FILE*) /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200802/work/gcc-11-20200802/gcc/lra.c:2415 0xbbea4c do_reload /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200802/work/gcc-11-20200802/gcc/ira.c:5525 0xbbea4c execute /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20200802/work/gcc-11-20200802/gcc/ira.c:5711
next reply other threads:[~2020-08-04 3:15 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-04 3:15 asolokha at gmx dot com [this message] 2020-08-04 6:05 ` [Bug target/96448] " rguenth at gcc dot gnu.org 2020-08-04 6:07 ` pinskia at gcc dot gnu.org 2022-10-19 4:03 ` asolokha at gmx dot com
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-96448-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: linkBe 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).