public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96163] New: another ice in pass slp Date: Sat, 11 Jul 2020 08:02:11 +0000 [thread overview] Message-ID: <bug-96163-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96163 Bug ID: 96163 Summary: another ice in pass slp Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- Created attachment 48862 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48862&action=edit C++ source code For the attached C++ source code with flag -O3, recent gcc trunk does this: /home/dcb/gcc/results.20200630/bin/g++ /home/dcb/gcc/results.20200701/bin/g++ bug630.cc: In function ‘void cm()’: bug630.cc:139:6: error: definition in block 2 follows the use 139 | void cm() { | ^~ for SSA_NAME: vect_cst__16 in statement: vect__2.37_17 = _14 / vect_cst__16; during GIMPLE pass: slp bug630.cc:139:6: internal compiler error: verify_ssa failed 0x13fb41b verify_ssa(bool, bool) ../../trunk.git/gcc/tree-ssa.c:1208 0x108dbf5 execute_function_todo ../../trunk.git/gcc/passes.c:1992 Trunk dated 20200630 is fine, 20200701 not.
next reply other threads:[~2020-07-11 8:02 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-11 8:02 dcb314 at hotmail dot com [this message] 2020-07-13 7:59 ` [Bug tree-optimization/96163] " rguenth at gcc dot gnu.org 2020-07-13 8:42 ` rguenth at gcc dot gnu.org 2020-07-13 14:50 ` cvs-commit at gcc dot gnu.org 2020-07-13 14:50 ` rguenth 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-96163-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).