public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/94700] New: ICE in forwprop when folding to a VEC_PERM_EXPR Date: Tue, 21 Apr 2020 18:29:05 +0000 [thread overview] Message-ID: <bug-94700-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94700 Bug ID: 94700 Summary: ICE in forwprop when folding to a VEC_PERM_EXPR Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: rsandifo at gcc dot gnu.org Target Milestone: --- Compiling this with -march=armv8.2-a+sve -msve-vector-bits=256 -O3: #include <arm_sve.h> typedef float v8sf __attribute__((vector_size(32))); svfloat32_t f (svbool_t pg, svfloat32_t x, svfloat32_t y) { v8sf a = svadd_x (pg, x, 1); v8sf b = { a[0], a[1], a[2], a[3], a[4], a[5], a[6], a[7] }; return svdiv_x (pg, b, y); } gives: foo.c: In function ‘svfloat32_t f(svbool_t, svfloat32_t, svfloat32_t)’: foo.c:11:1: error: non-trivial conversion in ‘ssa_name’ 11 | } | ^ v8sf __SVFloat32_t b_18 = _1; during GIMPLE pass: forwprop dump file: foo.031t.forwprop1 This is the maybe_ident equivalent of PR94683. I should have realised at the time that both arms would need fixing.
next reply other threads:[~2020-04-21 18:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-21 18:29 rsandifo at gcc dot gnu.org [this message] 2020-04-21 18:29 ` [Bug tree-optimization/94700] " rsandifo at gcc dot gnu.org 2020-04-22 10:06 ` cvs-commit at gcc dot gnu.org 2020-04-22 10:06 ` rsandifo 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-94700-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).