public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gil.hur at sf dot snu.ac.kr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/65752] Too strong optimizations int -> pointer casts Date: Mon, 18 May 2015 17:13:00 -0000 [thread overview] Message-ID: <bug-65752-4-YYtFKduxRp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65752-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65752 Chung-Kil Hur <gil.hur at sf dot snu.ac.kr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gil.hur at sf dot snu.ac.kr --- Comment #13 from Chung-Kil Hur <gil.hur at sf dot snu.ac.kr> --- Hi, I have the following modified code. #include <stdio.h> #include <stdint.h> #include <limits.h> int main() { int x = 0, *p = 0; uintptr_t i; uintptr_t j = (uintptr_t) &x; uintptr_t k = j+j; uintptr_t l = 2*j - j - j; for (i = j+j-k+l; ; i++) { if (i == (uintptr_t)&x) { p = (int*)i; break; } } *p = 15; printf("%d\n", x); } This example still prints out "0" instead of "15". In this example, it seems that the integer "j+j-k+l" has no provenance. It is unclear to me how the provenance is calculated. Is there any concrete rule for calculating provenance?
next prev parent reply other threads:[~2015-05-18 17:13 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-13 14:04 [Bug c/65752] New: " gcc at robbertkrebbers dot nl 2015-04-13 17:38 ` [Bug c/65752] " joseph at codesourcery dot com 2015-04-13 23:25 ` gcc at robbertkrebbers dot nl 2015-04-13 23:25 ` gcc at robbertkrebbers dot nl 2015-04-14 8:39 ` rguenth at gcc dot gnu.org 2015-04-14 8:46 ` gcc at robbertkrebbers dot nl 2015-04-14 9:01 ` rguenth at gcc dot gnu.org 2015-04-14 9:06 ` rguenth at gcc dot gnu.org 2015-04-14 9:23 ` gcc at robbertkrebbers dot nl 2015-04-14 9:26 ` gcc at robbertkrebbers dot nl 2015-04-14 10:50 ` rguenth at gcc dot gnu.org 2015-04-20 13:45 ` [Bug tree-optimization/65752] " mpolacek at gcc dot gnu.org 2015-04-20 13:53 ` gcc at robbertkrebbers dot nl 2015-05-18 17:13 ` gil.hur at sf dot snu.ac.kr [this message] 2015-05-19 9:21 ` rguenth at gcc dot gnu.org 2015-05-19 12:08 ` gil.hur at sf dot snu.ac.kr 2015-05-19 12:33 ` rguenth at gcc dot gnu.org 2015-05-19 13:14 ` gil.hur at sf dot snu.ac.kr 2015-05-19 14:21 ` rguenther at suse dot de 2015-05-19 14:29 ` gil.hur at sf dot snu.ac.kr 2015-05-19 14:32 ` mpolacek at gcc dot gnu.org 2015-05-19 15:12 ` gil.hur at sf dot snu.ac.kr 2015-05-19 15:23 ` Andreas Schwab 2015-05-19 15:23 ` schwab at suse dot de 2015-05-19 15:29 ` gil.hur at sf dot snu.ac.kr 2015-05-20 8:01 ` rguenth at gcc dot gnu.org 2015-05-20 10:55 ` gil.hur at sf dot snu.ac.kr 2015-05-20 11:20 ` gil.hur at sf dot snu.ac.kr 2015-05-20 11:33 ` rguenther at suse dot de 2015-05-22 4:55 ` mail at robbertkrebbers dot nl 2015-05-22 4:57 ` gcc at robbertkrebbers dot nl 2015-05-22 8:52 ` rguenth at gcc dot gnu.org 2015-05-23 8:14 ` gil.hur at sf dot snu.ac.kr 2015-05-26 11:26 ` rguenther at suse dot de 2015-05-26 13:55 ` gil.hur at sf dot snu.ac.kr 2015-05-26 14:00 ` rguenther at suse dot de 2015-05-26 14:06 ` gil.hur at sf dot snu.ac.kr 2020-08-04 21:31 ` tavianator at gmail dot com 2020-08-05 7:07 ` rguenther at suse dot de
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-65752-4-YYtFKduxRp@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).