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/98793] [11 Regression] wrong code with --param=max-jump-thread-duplication-stmts=4 since r11-6468-g01da03c915f086fb Date: Fri, 22 Jan 2021 14:24:03 +0000 [thread overview] Message-ID: <bug-98793-4-JWv9fKFkjv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98793-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98793 --- Comment #5 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:4be156d6bef317b8704052f11431457a577ed564 commit r11-6859-g4be156d6bef317b8704052f11431457a577ed564 Author: Richard Biener <rguenther@suse.de> Date: Fri Jan 22 14:32:39 2021 +0100 middle-end/98793 - properly handle BLKmode vectors in vector_element_bits The previous change made AVX512 mask vectors correct but disregarded the possibility of generic (BLKmode) boolean vectors which are exposed by the frontends already. 2021-01-22 Richard Biener <rguenther@suse.de> PR middle-end/98793 * tree.c (vector_element_bits): Key single-bit bool vector on integer mode rather than not vector mode. * gcc.dg/pr98793.c: New testcase.
next prev parent reply other threads:[~2021-01-22 14:24 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-22 11:36 [Bug rtl-optimization/98793] New: [11 Regression] wrong code with --param=max-jump-thread-duplication-stmts=4 zsojka at seznam dot cz 2021-01-22 12:33 ` [Bug tree-optimization/98793] " rguenth at gcc dot gnu.org 2021-01-22 12:51 ` rguenth at gcc dot gnu.org 2021-01-22 13:06 ` [Bug tree-optimization/98793] [11 Regression] wrong code with --param=max-jump-thread-duplication-stmts=4 since r11-6468-g01da03c915f086fb marxin at gcc dot gnu.org 2021-01-22 13:32 ` rguenth at gcc dot gnu.org 2021-01-22 14:24 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-22 14:24 ` 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-98793-4-JWv9fKFkjv@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).