public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94308] New: [10 Regression] ICE in final_scan_insn_1 with vzeroupper Date: Tue, 24 Mar 2020 18:25:21 +0000 [thread overview] Message-ID: <bug-94308-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94308 Bug ID: 94308 Summary: [10 Regression] ICE in final_scan_insn_1 with vzeroupper Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- /* { dg-do compile } */ /* { dg-options "-O2 -mfpmath=sse -mavx2 -mfma" } */ #include <x86intrin.h> void foo (float *x, const float *y, const float *z, unsigned int w) { unsigned int a; const unsigned int b = w / 8; const float *c = y; const float *d = z; __m256 e = _mm256_setzero_ps (); __m256 f, g; for (a = 0; a < b; a++) { f = _mm256_loadu_ps (c); g = _mm256_loadu_ps (d); c += 8; d += 8; e = _mm256_fmadd_ps (f, g, e); } __attribute__ ((aligned (32))) float h[8]; _mm256_storeu_ps (h, e); _mm256_zeroupper (); float i = h[0] + h[1] + h[2] + h[3] + h[4] + h[5] + h[6] + h[7]; for (a = b * 8; a < w; a++) i += (*c++) * (*d++); *x = i; } ICEs on i686-linux or x86_64-linux with -m32. The problem is that the vzeroupper pass in this case fills in sets for all xmm0..xmm7 regs, but doesn't force rerecognition of the insn, so it is still considered avx_vzeroupper_1, but the splitter doesn't trigger for it.
next reply other threads:[~2020-03-24 18:25 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-24 18:25 jakub at gcc dot gnu.org [this message] 2020-03-24 18:31 ` [Bug target/94308] [10 Regression] ICE in final_scan_insn_1 with vzeroupper since r10-6451 jakub at gcc dot gnu.org 2020-03-24 18:35 ` jakub at gcc dot gnu.org 2020-03-25 7:36 ` rguenth at gcc dot gnu.org 2020-03-25 10:40 ` cvs-commit at gcc dot gnu.org 2020-03-25 10:42 ` jakub 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-94308-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).