public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/96091] ICE during dom: tree check: expected integer_cst, have poly_int_cst in to_wide, at tree.h:5911 Date: Tue, 07 Jul 2020 07:30:00 +0000 [thread overview] Message-ID: <bug-96091-4-05Ip2oClTi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96091-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96091 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rsandifo at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Why should we not have a VECTOR_CST of POLY_INT_CST elements? If POLY_INT_CST is not "constant" then it shouldn't be tcc_constant? Looks like tree vector_cst_elt (const_tree t, unsigned int i) { ... /* Otherwise work out the value from the last two encoded elements. */ return wide_int_to_tree (TREE_TYPE (TREE_TYPE (t)), vector_cst_int_elt (t, i)); } should be using poly-ints and not wide-ints. Richard?
next prev parent reply other threads:[~2020-07-07 7:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-07 3:30 [Bug tree-optimization/96091] New: " qianchao9 at huawei dot com 2020-07-07 3:32 ` [Bug tree-optimization/96091] " qianchao9 at huawei dot com 2020-07-07 7:30 ` rguenth at gcc dot gnu.org [this message] 2020-07-07 7:39 ` rsandifo at gcc dot gnu.org 2021-12-12 13:18 ` pinskia 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-96091-4-05Ip2oClTi@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).