public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111751] RISC-V: RVV unexpected vectorization Date: Tue, 10 Oct 2023 12:20:15 +0000 [thread overview] Message-ID: <bug-111751-4-LsXps8mfYV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111751-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111751 --- Comment #19 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:70b5c6981fcdff246f90e57e91f3e1667eab2eb3 commit r14-4537-g70b5c6981fcdff246f90e57e91f3e1667eab2eb3 Author: Richard Biener <rguenther@suse.de> Date: Tue Oct 10 13:33:34 2023 +0200 tree-optimization/111751 - support 1024 bit vector constant reinterpretation The following ups the limit in fold_view_convert_expr to handle 1024bit vectors as used by GCN and RVV. It also robustifies the handling in visit_reference_op_load to properly give up when constants cannot be re-interpreted. PR tree-optimization/111751 * fold-const.cc (fold_view_convert_expr): Up the buffer size to 128 bytes. * tree-ssa-sccvn.cc (visit_reference_op_load): Special case constants, giving up when re-interpretation to the target type fails.
next prev parent reply other threads:[~2023-10-10 12:20 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-10 3:19 [Bug c/111751] New: " juzhe.zhong at rivai dot ai 2023-10-10 3:35 ` [Bug tree-optimization/111751] " pinskia at gcc dot gnu.org 2023-10-10 3:35 ` pinskia at gcc dot gnu.org 2023-10-10 3:36 ` pinskia at gcc dot gnu.org 2023-10-10 3:41 ` pinskia at gcc dot gnu.org 2023-10-10 3:51 ` juzhe.zhong at rivai dot ai 2023-10-10 3:55 ` pinskia at gcc dot gnu.org 2023-10-10 4:00 ` juzhe.zhong at rivai dot ai 2023-10-10 9:09 ` rguenth at gcc dot gnu.org 2023-10-10 9:24 ` juzhe.zhong at rivai dot ai 2023-10-10 9:32 ` rguenther at suse dot de 2023-10-10 10:38 ` cvs-commit at gcc dot gnu.org 2023-10-10 10:50 ` rguenth at gcc dot gnu.org 2023-10-10 11:17 ` juzhe.zhong at rivai dot ai 2023-10-10 11:23 ` juzhe.zhong at rivai dot ai 2023-10-10 11:40 ` juzhe.zhong at rivai dot ai 2023-10-10 11:49 ` rguenth at gcc dot gnu.org 2023-10-10 11:50 ` cvs-commit at gcc dot gnu.org 2023-10-10 11:56 ` juzhe.zhong at rivai dot ai 2023-10-10 12:20 ` cvs-commit at gcc dot gnu.org [this message] 2023-10-10 12:22 ` cvs-commit at gcc dot gnu.org 2023-10-10 12:47 ` juzhe.zhong at rivai dot ai
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-111751-4-LsXps8mfYV@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).