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 tree-optimization/87325] determine_base_object does not consider consider address space of base expr Date: Tue, 05 Dec 2023 12:47:35 +0000 [thread overview] Message-ID: <bug-87325-4-o4hVA3EXEb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-87325-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87325 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING Last reconfirmed|2018-09-17 00:00:00 |2023-12-5 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- It now works "better": <bb 3> [local count: 201326592]: ivtmp.7_24 = (<unnamed-unsigned:24>) &ts; <bb 4> [local count: 805306368]: # i_20 = PHI <i_15(6), 0(3)> # ivtmp.7_26 = PHI <ivtmp.7_25(6), ivtmp.7_24(3)> _29 = (<address-space-7> void *) ivtmp.7_26; _30 = _29 + 4; _1 = MEM[(float *)_30]; _2 = MEM[(float *)_29]; _3 = bar (_2, _1); r = _3; _17 = ivtmp.7_26 + 8; _4 = (const <address-space-7> float *) _17; _5 = (const float *) _4; _6 = foo (&r, _5); if (_6 != 0) note the (implicit) address-space convert for the 2nd argument to foo (), the testcase may be actually invalid. The linked bug is still there, but this one might be fixed by r14-6133-ge00c00730912cd? Please verify and close if fixed. PR60075 tracks a remaining IVOPTs issue.
parent reply other threads:[~2023-12-05 12:47 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <bug-87325-4@http.gcc.gnu.org/bugzilla/>]
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-87325-4-o4hVA3EXEb@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).