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/98381] [11 Regression] Wrong code with -O3 -march=skylake-avx512 by r11-3072 Date: Tue, 05 Jan 2021 14:54:56 +0000 [thread overview] Message-ID: <bug-98381-4-FmHduilSVp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98381-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98381 --- Comment #3 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:01da03c915f086fb9aa36b809c1a06a9f661533b commit r11-6468-g01da03c915f086fb9aa36b809c1a06a9f661533b Author: Richard Biener <rguenther@suse.de> Date: Tue Jan 5 14:23:55 2021 +0100 tree-optimization/98381 - fix live bool vector extract This fixes extraction of live bool vector results for the case of integer mode vectors. 2021-01-05 Richard Biener <rguenther@suse.de> PR tree-optimization/98381 * tree.c (vector_element_bits): Properly compute bool vector element size. * tree-vect-loop.c (vectorizable_live_operation): Properly compute the last lane bit offset.
next prev parent reply other threads:[~2021-01-05 14:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-18 20:03 [Bug tree-optimization/98381] New: Wrong code with -O3 -march=skylake-avx512 vsevolod.livinskij at frtk dot ru 2020-12-19 14:18 ` [Bug tree-optimization/98381] [11 Regression] Wrong code with -O3 -march=skylake-avx512 by r11-3072 hjl.tools at gmail dot com 2020-12-21 8:29 ` marxin at gcc dot gnu.org 2021-01-04 9:03 ` rguenth at gcc dot gnu.org 2021-01-05 14:54 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-05 14:56 ` 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-98381-4-FmHduilSVp@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).