public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/94988] [11 Regression] FAIL: gcc.target/i386/pr64110.c scan-assembler vmovd[\\t ] Date: Fri, 08 May 2020 06:31:17 +0000 [thread overview] Message-ID: <bug-94988-4-js0bSusltY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94988-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94988 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Last reconfirmed| |2020-05-08 Status|UNCONFIRMED |ASSIGNED Blocks| |57359 Target Milestone|--- |11.0 Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Ah, forgot to update this testcase. This is another instance of PR57359, that is, we may not sink the store to b across the store to *b since b may point to itself and with j == 1 we'd change b = b + 2; *b = x; to *b = x; b = b + 2; note there's a twist for this particular case, namely the preceeding load of 'b' gives us knowledge about the dynamic type of 'b' which means we could use that to assess that we _can_ exchange the stores. But that logic is not implemented. I'll see how to do that. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57359 [Bug 57359] store motion causes wrong code for union access at -O3
next prev parent reply other threads:[~2020-05-08 6:31 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-07 18:29 [Bug middle-end/94988] New: " hjl.tools at gmail dot com 2020-05-08 6:31 ` rguenth at gcc dot gnu.org [this message] 2020-05-08 10:08 ` [Bug middle-end/94988] " rguenth at gcc dot gnu.org 2020-05-11 14:53 ` cvs-commit at gcc dot gnu.org 2020-05-11 14:57 ` rguenth at gcc dot gnu.org 2020-05-12 11:53 ` ro at gcc dot gnu.org 2020-05-12 12:12 ` cvs-commit at gcc dot gnu.org 2020-05-12 12:13 ` rguenth at gcc dot gnu.org 2020-06-16 11:32 ` cvs-commit at gcc dot gnu.org 2024-02-15 18:20 ` aoliva at gcc dot gnu.org 2024-02-15 18:36 ` aoliva at gcc dot gnu.org 2024-02-16 7:49 ` 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-94988-4-js0bSusltY@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).