public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/107107] Wrong codegen from TBAA when stores to distinct same-mode types are collapsed? Date: Sat, 01 Oct 2022 03:02:11 +0000 [thread overview] Message-ID: <bug-107107-4-MhtTGqLjXD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107107-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107107 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |4.1.2, 4.4.7, 4.5.3 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Here is a testcase which has failed since before 4.1.2: ``` static inline void set_longish(int is_long_long, void *p, long x) { if (is_long_long) *(long long*)p = x; else *(long*)p = x; } static long test(long long *p, int index, int mode) { *p = 1; set_longish(mode, p+index, 2); return *p; } long (*volatile vtest)(long long*, int, int) = test; #include <stdio.h> int main(void) { long long x; long result = vtest(&x, 0, 1); printf("%lu/%llu\n", result, x); } ``` The only difference from the original testcase is marking set_longish as static inline. I suspect what changed between 4.7 and 4.8 for the original testcase is inlining.
next prev parent reply other threads:[~2022-10-01 3:02 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-30 21:34 [Bug middle-end/107107] New: " bugdal at aerifal dot cx 2022-10-01 2:25 ` [Bug middle-end/107107] " bugdal at aerifal dot cx 2022-10-01 2:59 ` pinskia at gcc dot gnu.org 2022-10-01 3:02 ` pinskia at gcc dot gnu.org [this message] 2022-10-01 3:05 ` [Bug tree-optimization/107107] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-10-01 3:05 ` pinskia at gcc dot gnu.org 2022-10-01 17:08 ` amonakov at gcc dot gnu.org 2022-10-01 20:01 ` bugdal at aerifal dot cx 2022-10-06 9:02 ` rguenth at gcc dot gnu.org 2022-10-06 9:22 ` rguenth at gcc dot gnu.org 2022-10-06 10:07 ` cvs-commit at gcc dot gnu.org 2022-10-06 10:08 ` [Bug tree-optimization/107107] [10/11/12 " rguenth at gcc dot gnu.org 2022-10-17 13:10 ` cvs-commit at gcc dot gnu.org 2022-12-12 16:33 ` [Bug tree-optimization/107107] [10/11 " cvs-commit at gcc dot gnu.org 2023-01-26 13:05 ` [Bug tree-optimization/107107] [10 " cvs-commit at gcc dot gnu.org 2023-01-26 13:06 ` 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-107107-4-MhtTGqLjXD@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).