public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108008] [12 Regression] wrong code with -O3 and posix_memalign Date: Thu, 08 Dec 2022 08:44:48 +0000 [thread overview] Message-ID: <bug-108008-4-kVmGNVfw2x@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108008-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108008 --- Comment #9 from Alexander Monakov <amonakov at gcc dot gnu.org> --- I think this is tree-ldist placing memset(sameZ, 0, zPlaneCount) after the loop, overwriting conditional 'sameZ[i] = true' assignments that happen in the loop. For the smaller testcase from comment #6, -O2 -ftree-loop-distribution is enough, namely: works: gcc-12 -O2 -ftree-loop-distribution -fno-tree-vectorize -fno-tree-loop-distribute-patterns breaks: gcc-12 -O2 -ftree-loop-distribution -fno-tree-vectorize
next prev parent reply other threads:[~2022-12-08 8:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-07 14:06 [Bug c++/108008] New: Compiler mis-optimization with posix_memalign hahnjo at hahnjo dot de 2022-12-07 14:43 ` [Bug c++/108008] " amonakov at gcc dot gnu.org 2022-12-07 22:12 ` [Bug tree-optimization/108008] " dhsbz at chaw dot com 2022-12-07 22:24 ` pinskia at gcc dot gnu.org 2022-12-07 22:37 ` pinskia at gcc dot gnu.org 2022-12-07 22:48 ` pinskia at gcc dot gnu.org 2022-12-07 22:58 ` pinskia at gcc dot gnu.org 2022-12-07 23:05 ` [Bug tree-optimization/108008] [12 Regression] " pinskia at gcc dot gnu.org 2022-12-07 23:05 ` pinskia at gcc dot gnu.org 2022-12-08 8:44 ` amonakov at gcc dot gnu.org [this message] 2022-12-12 7:38 ` [Bug tree-optimization/108008] [12 Regression] wrong code with -O3 and posix_memalign amonakov at gcc dot gnu.org 2022-12-27 14:22 ` marxin at gcc dot gnu.org 2022-12-27 14:23 ` [Bug tree-optimization/108008] [12 Regression] wrong code with -O3 and posix_memalign since r12-4526-gd8edfadfc7a9795b marxin at gcc dot gnu.org 2023-01-09 12:48 ` rguenth at gcc dot gnu.org 2023-01-09 15:06 ` marxin at gcc dot gnu.org 2023-01-10 8:00 ` 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-108008-4-kVmGNVfw2x@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).