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 middle-end/110495] fre introduces signed wrap for vector Date: Mon, 03 Jul 2023 08:40:42 +0000 [thread overview] Message-ID: <bug-110495-4-mKgibIhNKk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110495-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110495 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- OK, that's a reasonable stance give we have VL vectors. I'll note that previously build_vector looked like the following, so TREE_OVERFLOW was set according to the encoded elements. Now that's no longer the case. I'll post a patch for comments. /* Return a new VECTOR_CST node whose type is TYPE and whose values are in a list pointed to by VALS. */ tree build_vector_stat (tree type, tree *vals MEM_STAT_DECL) { int over = 0; unsigned cnt = 0; tree v = make_vector (TYPE_VECTOR_SUBPARTS (type)); TREE_TYPE (v) = type; /* Iterate through elements and check for overflow. */ for (cnt = 0; cnt < TYPE_VECTOR_SUBPARTS (type); ++cnt) { tree value = vals[cnt]; VECTOR_CST_ELT (v, cnt) = value; /* Don't crash if we get an address constant. */ if (!CONSTANT_CLASS_P (value)) continue; over |= TREE_OVERFLOW (value); } TREE_OVERFLOW (v) = over; return v;
next prev parent reply other threads:[~2023-07-03 8:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-30 9:06 [Bug tree-optimization/110495] New: " kristerw at gcc dot gnu.org 2023-06-30 9:33 ` [Bug middle-end/110495] " rguenth at gcc dot gnu.org 2023-07-03 8:09 ` rsandifo at gcc dot gnu.org 2023-07-03 8:40 ` rguenth at gcc dot gnu.org [this message] 2023-07-03 8:43 ` rguenth at gcc dot gnu.org 2023-07-04 7:08 ` cvs-commit at gcc dot gnu.org 2023-07-04 7:09 ` 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-110495-4-mKgibIhNKk@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).