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: Tue, 16 May 2023 02:42:21 +0000 [thread overview]
Message-ID: <bug-77899-4-Mp6Ulq2HYe@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
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=107699
--- Comment #13 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #12)
> 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 ();
> }
That was handled by r13-4555-g892e8c520be37d (aka PR 107699).
The non eq/ne ones are not handled though; I think there might be another bug
about that ...
prev parent reply other threads:[~2023-05-16 2:42 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
2023-05-16 2:42 ` pinskia at gcc dot gnu.org [this message]
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-Mp6Ulq2HYe@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: link
Be 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).