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/51074] No constant folding performed for VEC_PERM_EXPR, VEC_INTERLEAVE*EXPR, VEC_EXTRACT*EXPR Date: Thu, 10 Nov 2011 10:43:00 -0000 [thread overview] Message-ID: <bug-51074-4-7BSfLetPtx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51074-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51074 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011-11-10 Ever Confirmed|0 |1 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-11-10 10:40:20 UTC --- Well, why not handle the tree codes in fold-const.c? That way all propagators would handle it via gimple_fold_stmt_to_constant_1.
next prev parent reply other threads:[~2011-11-10 10:41 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-10 9:37 [Bug tree-optimization/51074] New: " jakub at gcc dot gnu.org 2011-11-10 10:43 ` rguenth at gcc dot gnu.org [this message] 2011-11-10 10:54 ` [Bug tree-optimization/51074] " jakub at gcc dot gnu.org 2011-11-10 14:05 ` jakub at gcc dot gnu.org 2011-11-10 14:06 ` rguenth at gcc dot gnu.org 2011-11-11 19:58 ` jakub at gcc dot gnu.org 2011-11-22 1:39 ` pthaugen at gcc dot gnu.org 2011-11-22 10:50 ` jakub at gcc dot gnu.org 2011-11-22 16:35 ` rth at gcc dot gnu.org 2011-11-22 16:43 ` pthaugen at gcc dot gnu.org 2011-11-22 17:54 ` jakub at gcc dot gnu.org 2021-07-21 2:49 ` 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-51074-4-7BSfLetPtx@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).