public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109469] [13 regression] ICE: internal compiler error: verify_flow_info failed (error: returns_twice call is not first in basic block 2) Date: Tue, 11 Apr 2023 13:11:08 +0000 [thread overview] Message-ID: <bug-109469-4-OMkl1aJuuN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109469-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109469 Alexander Monakov <amonakov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amonakov at gcc dot gnu.org --- Comment #6 from Alexander Monakov <amonakov at gcc dot gnu.org> --- Not a dup. Why is SLP emitting a vector construction in BB 2 and not BB 4? (-fno-tree-slp-vectorize disables it): void dummy_write_proc () { + void (*<T24b>) () * vectp.4; + vector(2) long unsigned int * {ref-all} vectp_myproc.3; + long unsigned int _7; + long unsigned int _8; + vector(2) long unsigned int _9; + <bb 2> [local count: 1073741824]: + _7 = VIEW_CONVERT_EXPR<long unsigned int>(dummy_write_proc); + _8 = VIEW_CONVERT_EXPR<long unsigned int>(dummy_write_proc); + _9 = {_8, _7}; # DEBUG BEGIN_STMT foo (); goto <bb 4>; [99.96%] <bb 3> [local count: 429496]: .ABNORMAL_DISPATCHER (0); <bb 4> [local count: 1073312329]: # DEBUG BEGIN_STMT - myproc.write_proc = dummy_write_proc; - myproc.read_proc = dummy_write_proc; + MEM <vector(2) long unsigned int> [(void (*<T24b>) () *)&myproc] = _9; return; }
next prev parent reply other threads:[~2023-04-11 13:11 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-11 6:39 [Bug tree-optimization/109469] New: " sjames at gcc dot gnu.org 2023-04-11 6:40 ` [Bug tree-optimization/109469] " sjames at gcc dot gnu.org 2023-04-11 6:40 ` sjames at gcc dot gnu.org 2023-04-11 6:41 ` sjames at gcc dot gnu.org 2023-04-11 6:41 ` sjames at gcc dot gnu.org 2023-04-11 6:43 ` sjames at gcc dot gnu.org 2023-04-11 13:11 ` amonakov at gcc dot gnu.org [this message] 2023-04-11 13:39 ` rguenth at gcc dot gnu.org 2023-04-12 6:05 ` [Bug tree-optimization/109469] [13 regression] ICE: internal compiler error: verify_flow_info failed (error: returns_twice call is not first in basic block 2) when building xdvik amonakov at gcc dot gnu.org 2023-04-12 6:49 ` cvs-commit at gcc dot gnu.org 2023-04-12 6:51 ` rguenth at gcc dot gnu.org 2023-04-12 6:51 ` rguenth at gcc dot gnu.org 2023-04-17 9:14 ` [Bug tree-optimization/109469] [12 " cvs-commit at gcc dot gnu.org 2023-04-17 9:17 ` 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-109469-4-OMkl1aJuuN@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).