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/102798] [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta by r9-2475 Date: Mon, 18 Oct 2021 08:26:29 +0000 [thread overview] Message-ID: <bug-102798-4-0dW4GFyBfW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102798-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102798 --- Comment #12 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:a5b1b2a186d94b31a522395e9d02c9cec1b928cb commit r12-4466-ga5b1b2a186d94b31a522395e9d02c9cec1b928cb Author: Richard Biener <rguenther@suse.de> Date: Mon Oct 18 09:10:43 2021 +0200 tree-optimization/102798 - avoid copying PTA info to old SSA names The vectorizer duplicates pointer-info to created pointer bases but it has to avoid changing points-to info on existing SSA names because there's now flow-sensitive info in there (pt->pt_null as set from VRP). 2021-10-18 Richard Biener <rguenther@suse.de> PR tree-optimization/102798 * tree-vect-data-refs.c (vect_create_addr_base_for_vector_ref): Only copy points-to info to newly generated SSA names. * gcc.dg/pr102798.c: New testcase.
next prev parent reply other threads:[~2021-10-18 8:26 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-16 12:43 [Bug target/102798] New: [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta -mavx512f zsojka at seznam dot cz 2021-10-16 15:54 ` [Bug tree-optimization/102798] [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta -mavx512f by r9-2475 hjl.tools at gmail dot com 2021-10-16 16:31 ` hjl.tools at gmail dot com 2021-10-16 18:10 ` hjl.tools at gmail dot com 2021-10-16 18:16 ` hjl.tools at gmail dot com 2021-10-16 18:42 ` pinskia at gcc dot gnu.org 2021-10-16 18:43 ` pinskia at gcc dot gnu.org 2021-10-16 18:46 ` [Bug tree-optimization/102798] [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta " pinskia at gcc dot gnu.org 2021-10-16 19:08 ` hjl.tools at gmail dot com 2021-10-17 0:53 ` hjl.tools at gmail dot com 2021-10-17 2:49 ` hjl.tools at gmail dot com 2021-10-17 13:33 ` hjl.tools at gmail dot com 2021-10-17 18:29 ` hjl.tools at gmail dot com 2021-10-18 6:39 ` rguenth at gcc dot gnu.org 2021-10-18 7:03 ` rguenth at gcc dot gnu.org 2021-10-18 8:26 ` cvs-commit at gcc dot gnu.org [this message] 2021-10-18 8:27 ` [Bug tree-optimization/102798] [9/10/11 " rguenth at gcc dot gnu.org 2021-11-08 13:32 ` cvs-commit at gcc dot gnu.org 2022-02-17 10:48 ` [Bug tree-optimization/102798] [9/10 " cvs-commit at gcc dot gnu.org 2022-02-17 11:57 ` [Bug tree-optimization/102798] [9 " cvs-commit at gcc dot gnu.org 2022-02-17 11:58 ` rguenth at gcc dot gnu.org 2022-02-18 7:10 ` rguenth at gcc dot gnu.org 2022-02-18 7:11 ` rguenth at gcc dot gnu.org 2022-02-18 7:13 ` rguenth at gcc dot gnu.org 2022-02-18 8:21 ` rguenth at gcc dot gnu.org 2022-02-18 8:22 ` 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-102798-4-0dW4GFyBfW@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).