public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/32575] [4.2/4.3 regression] With -ftree-vrp miscompiles a single line of code in SQLite Date: Tue, 28 Aug 2007 15:58:00 -0000 [thread overview] Message-ID: <20070828155829.23399.qmail@sourceware.org> (raw) In-Reply-To: <bug-32575-14787@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from jakub at gcc dot gnu dot org 2007-08-28 15:58 ------- if (a == 0) a = bar (); isn't necessary either. salias has: # BLOCK 2 freq:10000 # PRED: ENTRY [100.0%] (fallthru,exec) # VUSE <qD.2026_12(D), SMT.25D.2079_13(D)> { qD.2026 SMT.25D.2079 } D.2027_3 = foo (); pD.2025_4 = (struct S *) D.2027_3; if (pD.2025_4 == 0B) goto <bb 3>; else goto <bb 4>; # SUCC: 3 [7.3%] (true,exec) 4 [92.7%] (false,exec) # BLOCK 3 freq:735 # PRED: 2 [7.3%] (true,exec) # qD.2026_15 = VDEF <qD.2026_12(D)> # SMT.25D.2079_16 = VDEF <SMT.25D.2079_13(D)> # SMT.26D.2080_17 = VDEF <SMT.26D.2080_14(D)> { qD.2026 SMT.25D.2079 SMT.26D.2080 } __builtin_memset (&qD.2026, 0, 24); # SUCC: 4 [100.0%] (fallthru,exec) # BLOCK 4 freq:10000 # PRED: 2 [92.7%] (false,exec) 3 [100.0%] (fallthru,exec) # qD.2026_11 = PHI <qD.2026_12(D)(2), qD.2026_15(3)> # pD.2025_1 = PHI <pD.2025_4(2), &qD.2026(3)> # qD.2026_18 = VDEF <qD.2026_11> { qD.2026 } pD.2025_1->s1D.2008 = aD.2021_6(D); # qD.2026_19 = VDEF <qD.2026_18> { qD.2026 } pD.2025_1->s2D.2009 = bD.2022_7(D); Shouldn't the VDEFs be a PHI of some SMT and qD? pD.2025_1 can either be what foo returned, or it can point to the automatic variable q. -- jakub at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.2.2 |--- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32575
next prev parent reply other threads:[~2007-08-28 15:58 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-01 22:07 [Bug c/32575] New: GCC 4.3.0 with " drh at sqlite dot org 2007-07-01 22:16 ` [Bug tree-optimization/32575] " pinskia at gcc dot gnu dot org 2007-07-01 22:52 ` [Bug c/32575] " drh at sqlite dot org 2007-07-01 23:01 ` [Bug c/32575] GCC 4.2.0 " pinskia at gcc dot gnu dot org 2007-07-22 11:43 ` drh at sqlite dot org 2007-08-28 14:55 ` [Bug c/32575] [4.2/4.3 regression] With " jakub at gcc dot gnu dot org 2007-08-28 15:16 ` jakub at gcc dot gnu dot org 2007-08-28 15:58 ` jakub at gcc dot gnu dot org [this message] 2007-09-05 11:50 ` Daniel Berlin 2007-08-30 21:19 ` [Bug middle-end/32575] " pinskia at gcc dot gnu dot org 2007-09-05 0:56 ` mmitchel at gcc dot gnu dot org 2007-09-05 11:51 ` dberlin at dberlin dot org 2007-09-07 14:14 ` rguenth at gcc dot gnu dot org 2007-09-10 18:39 ` [Bug tree-optimization/32575] " jakub at gcc dot gnu dot org 2007-10-09 19:30 ` mmitchel at gcc dot gnu dot org 2007-11-01 14:03 ` nickc at redhat dot com 2007-11-01 14:06 ` nickc at redhat dot com 2007-11-01 14:34 ` jakub at gcc dot gnu dot org 2007-11-01 14:57 ` nickc at redhat dot com 2007-11-01 15:05 ` rguenth at gcc dot gnu dot org 2007-11-08 12:54 ` jakub at gcc dot gnu dot org 2007-11-08 13:08 ` jakub at gcc dot gnu dot org 2007-11-08 13:12 ` [Bug tree-optimization/32575] [4.2 " jakub at gcc dot gnu dot org 2008-02-01 17:05 ` jsm28 at gcc dot gnu dot org 2008-05-19 20:30 ` jsm28 at gcc dot gnu dot org 2009-03-30 22:11 ` jsm28 at gcc dot gnu dot 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=20070828155829.23399.qmail@sourceware.org \ --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).