From: Jeff Law <jlaw@ventanamicro.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] [PR tree-optimization/92539] Optimize away tests against invalid pointers
Date: Sun, 10 Mar 2024 15:09:18 -0600 [thread overview]
Message-ID: <61bfe66a-6e08-4ca9-9f0a-81082762e702@ventanamicro.com> (raw)
In-Reply-To: <CA+=Sn1mjgKvohVmr8pgNM+tvrX3-feSPGhOK=Muer-D47qSdHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
On 3/10/24 3:05 PM, Andrew Pinski wrote:
> On Sun, Mar 10, 2024 at 2:04 PM Jeff Law <jlaw@ventanamicro.com> wrote:
>>
>> Here's a potential approach to fixing PR92539, a P2 -Warray-bounds false
>> positive triggered by loop unrolling.
>>
>> As I speculated a couple years ago, we could eliminate the comparisons
>> against bogus pointers. Consider:
>>
>>> <bb 8> [local count: 30530247]:
>>> if (last_12 != &MEM <const char> [(void *)"aa" + 3B])
>>> goto <bb 9>; [54.59%]
>>> else
>>> goto <bb 12>; [45.41%]
>>
>>
>> That's a valid comparison as ISO allows us to generate, but not
>> dereference, a pointer one element past the end of the object.
>>
>> But +4B is a bogus pointer. So given an EQ comparison against that
>> pointer we could always return false and for NE always return true.
>>
>> VRP and DOM seem to be the most natural choices for this kind of
>> optimization on the surface. However DOM is actually not viable because
>> the out-of-bounds pointer warning pass is run at the end of VRP. So
>> we've got to take care of this prior to the end of VRP.
>>
>>
>>
>> I haven't done a bootstrap or regression test with this. But if it
>> looks reasonable I can certainly push on it further. I have confirmed it
>> does eliminate the tests and shuts up the bogus warning.
>>
>> The downside is this would also shut up valid warnings if user code did
>> this kind of test.
>>
>> Comments/Suggestions?
>
> ENOPATCH
Yea, realized it as I pushed the send button. Then t-bird crashed,
repeatedly.
Attached this time..
jeff
[-- Attachment #2: P --]
[-- Type: text/plain, Size: 1270 bytes --]
diff --git a/gcc/vr-values.cc b/gcc/vr-values.cc
index 3ccb77d28be..cc753e79a8a 100644
--- a/gcc/vr-values.cc
+++ b/gcc/vr-values.cc
@@ -325,6 +325,34 @@ simplify_using_ranges::fold_cond_with_ops (enum tree_code code,
if (res == range_false (type))
return boolean_false_node;
}
+
+ /* If we're comparing pointers and one of the pointers is
+ not a valid pointer (say &MEM <const char> [(void *)"aa" + 4B)
+ return true for EQ and false for NE. */
+ if ((code == EQ_EXPR || code == NE_EXPR)
+ && POINTER_TYPE_P (type)
+ && TREE_CODE (op1) == ADDR_EXPR
+ && TREE_CODE (TREE_OPERAND (op1, 0)) == MEM_REF)
+ {
+ tree mem_ref = TREE_OPERAND (op1, 0);
+ if (TREE_CODE (TREE_OPERAND (mem_ref, 0)) == ADDR_EXPR)
+ {
+ tree addr_expr = TREE_OPERAND (mem_ref, 0);
+ if (TREE_CODE (TREE_OPERAND (addr_expr, 0)) == STRING_CST)
+ {
+ tree string = TREE_OPERAND (addr_expr, 0);
+
+ if (TREE_CODE (TREE_OPERAND (mem_ref, 1)) == INTEGER_CST)
+ {
+ HOST_WIDE_INT len = TREE_STRING_LENGTH (string);
+ HOST_WIDE_INT offset = tree_to_uhwi (TREE_OPERAND (mem_ref, 1));
+ if (offset > len)
+ return code == EQ_EXPR ? boolean_false_node : boolean_true_node;
+ }
+ }
+ }
+ }
+
return NULL;
}
next prev parent reply other threads:[~2024-03-10 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 21:03 Jeff Law
2024-03-10 21:05 ` Andrew Pinski
2024-03-10 21:09 ` Jeff Law [this message]
2024-03-11 3:19 ` Andrew Pinski
2024-03-11 7:46 ` Richard Biener
2024-03-11 7:57 ` Richard Biener
2024-03-12 0:18 ` Jeff Law
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=61bfe66a-6e08-4ca9-9f0a-81082762e702@ventanamicro.com \
--to=jlaw@ventanamicro.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
/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).