public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111683] [11/12/13/14 Regression] Incorrect answer when using SSE2 intrinsics with -O3 since r7-3163-g973625a04b3d9351f2485e37f7d3382af2aed87e Date: Fri, 22 Mar 2024 11:43:47 +0000 [thread overview] Message-ID: <bug-111683-4-Y4JL7kOsLj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111683-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111683 --- Comment #24 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Richard Biener from comment #23) > It looks like this could go to suitable_reference_p instead? You mean return false for those making them not suitable at all? I thought without a write such references would act more like RS_ANY, but a reason I didn't just treat such references as RS_ANY rather than RS_NONZERO in suitable_reference_p was because of the assert that all refs in a component have the same ref_step_type but nothing actually comparing it before the assertion. But if you think I should just return false from suitable_reference_p if the step isn't a multiple of the sizes, I can surely try that. > That said, I do wonder why with my patch split_data_refs_to_components > doesn't fixup. I think it's supposed to handle the case where > dependences are unknown conservatively... I'm afraid I'm not familiar with data refs enough to know what was going on.
next prev parent reply other threads:[~2024-03-22 11:43 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-03 18:27 [Bug c++/111683] New: Incorrect answer when using SSE2 intrinsics with -O3 deodharvinit99 at gmail dot com 2023-10-03 22:18 ` [Bug middle-end/111683] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-10-04 9:55 ` rguenth at gcc dot gnu.org 2023-10-04 16:56 ` amonakov at gcc dot gnu.org 2023-12-12 10:27 ` jakub at gcc dot gnu.org 2024-03-07 21:06 ` law at gcc dot gnu.org 2024-03-10 5:55 ` [Bug middle-end/111683] [11/12/13/14 Regression] Incorrect answer when using SSE2 intrinsics with -O3 since r7-3163-g973625a04b3d9351f2485e37f7d3382af2aed87e kugan at gcc dot gnu.org 2024-03-10 11:15 ` sjames at gcc dot gnu.org 2024-03-12 1:58 ` pinskia at gcc dot gnu.org 2024-03-12 2:24 ` pinskia at gcc dot gnu.org 2024-03-12 2:31 ` pinskia at gcc dot gnu.org 2024-03-12 2:44 ` pinskia at gcc dot gnu.org 2024-03-12 13:23 ` jakub at gcc dot gnu.org 2024-03-19 17:28 ` jakub at gcc dot gnu.org 2024-03-19 18:17 ` pinskia at gcc dot gnu.org 2024-03-21 16:47 ` jakub at gcc dot gnu.org 2024-03-22 7:33 ` rguenth at gcc dot gnu.org 2024-03-22 7:38 ` rguenth at gcc dot gnu.org 2024-03-22 7:47 ` jakub at gcc dot gnu.org 2024-03-22 7:50 ` jakub at gcc dot gnu.org 2024-03-22 8:06 ` rguenth at gcc dot gnu.org 2024-03-22 8:18 ` jakub at gcc dot gnu.org 2024-03-22 10:37 ` jakub at gcc dot gnu.org 2024-03-22 10:46 ` jakub at gcc dot gnu.org 2024-03-22 11:35 ` rguenth at gcc dot gnu.org 2024-03-22 11:43 ` jakub at gcc dot gnu.org [this message] 2024-03-22 12:42 ` rguenther at suse dot de 2024-03-23 10:18 ` cvs-commit at gcc dot gnu.org 2024-03-23 10:21 ` [Bug middle-end/111683] [11/12/13 " jakub at gcc dot gnu.org 2024-03-30 3:55 ` cvs-commit 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-111683-4-Y4JL7kOsLj@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).