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 tree-optimization/77899] incorrect VR_RANGE for a signed char function argument Date: Mon, 06 Sep 2021 11:32:22 +0000 [thread overview] Message-ID: <bug-77899-4-IzL5PrNf4i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-77899-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77899 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-09-06 Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #12 from Andrew Pinski <pinskia at gcc dot gnu.org> --- p_6 = &d[130] + _1; if (&MEM <char[260]> [(void *)&d + 2B] > p_6) Even this should be folded but is not currently: void f (signed char i) { char d [260]; const char *p = &d[130]; p += i; if (p == d + 2 || d + 257 == p) __builtin_abort (); } I am thinking ptr_difference_const is not able to handle &MEM <char[260]> [(void *)&d + 2B] correctly.
next prev parent reply other threads:[~2021-09-06 11:32 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-77899-4@http.gcc.gnu.org/bugzilla/> 2021-08-10 4:31 ` pinskia at gcc dot gnu.org 2021-09-06 11:32 ` pinskia at gcc dot gnu.org [this message] 2023-05-16 2:42 ` pinskia 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-77899-4-IzL5PrNf4i@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).