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/103961] [12 Regression] gcc-12 apparently miscompiles libcap's cap_to_text() function
Date: Mon, 10 Jan 2022 13:35:26 +0000 [thread overview]
Message-ID: <bug-103961-4-cnrpwQPrPH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103961-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103961
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> Looks like GCC is getting confused due to:
> p--;
>
>
> I don't get:
> [cap_text.c:419:3] # PT = anything
> _104 = p_65 + 18446744073709551615;
>
> All other places just have # PT = { D.4523 } (escaped)
>
> D.4523 being buf decl.
I think that might be ranger adding nonnull to a pointer where we previously
have no points-to info at all (which means anything as well). The above
stmt is introduced by PRE:
- <bb 81> [local count: 982087419]:
- goto <bb 21>; [100.00%]
+ <bb 94> [local count: 982087419]:
+ goto <bb 23>; [100.00%]
+
+ <bb 29> [local count: 37309945]:
+ [cap_text.c:419:3] _104 = p_65 + 18446744073709551615;
- <bb 27> [local count: 39298952]:
+ <bb 30> [local count: 39298952]:
# PT = { D.4523 } (escaped)
- # p_228 = PHI <p_65(26), [cap_text.c:403:4] p_147(20)>
- [cap_text.c:419:3] # PT = { D.4523 } (escaped)
- p_149 = p_228 + 18446744073709551615;
+ # p_228 = PHI <p_65(29), [cap_text.c:403:4] p_147(91)>
+ # PT = { D.4523 } (escaped)
+ # prephitmp_82 = PHI <_104(29), p_210(91)>
which could indeed have preserved points-to info (but it would need to be
tracked in the expression sets so that's not too easy).
next prev parent reply other threads:[~2022-01-10 13:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 12:33 [Bug c/103961] New: " manuel.lauss at googlemail dot com
2022-01-10 12:34 ` [Bug c/103961] " manuel.lauss at googlemail dot com
2022-01-10 12:34 ` manuel.lauss at googlemail dot com
2022-01-10 12:50 ` [Bug middle-end/103961] [12 Regression] " pinskia at gcc dot gnu.org
2022-01-10 13:06 ` pinskia at gcc dot gnu.org
2022-01-10 13:11 ` pinskia at gcc dot gnu.org
2022-01-10 13:12 ` pinskia at gcc dot gnu.org
2022-01-10 13:14 ` pinskia at gcc dot gnu.org
2022-01-10 13:19 ` [Bug tree-optimization/103961] " pinskia at gcc dot gnu.org
2022-01-10 13:35 ` rguenth at gcc dot gnu.org [this message]
2022-01-11 2:02 ` pinskia at gcc dot gnu.org
2022-01-11 2:12 ` pinskia at gcc dot gnu.org
2022-01-11 2:13 ` pinskia at gcc dot gnu.org
2022-01-11 9:10 ` [Bug tree-optimization/103961] [12 Regression] gcc-12 apparently miscompiles libcap's cap_to_text() function since r12-6030-g422f9eb7011b76c1 marxin at gcc dot gnu.org
2022-01-11 9:18 ` marxin at gcc dot gnu.org
2022-01-11 9:27 ` jakub at gcc dot gnu.org
2022-01-11 9:35 ` siddhesh at gcc dot gnu.org
2022-01-11 13:00 ` rguenth at gcc dot gnu.org
2022-01-11 14:48 ` cvs-commit at gcc dot gnu.org
2022-01-11 14:52 ` siddhesh at gcc dot gnu.org
2022-01-11 16:11 ` manuel.lauss at googlemail dot com
2022-01-11 16:20 ` jakub 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-103961-4-cnrpwQPrPH@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).