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 c++/53239] [4.7 Regression] -ftree-vrp breaks min() Date: Fri, 04 May 2012 21:54:00 -0000 [thread overview] Message-ID: <bug-53239-4-BfYgnQclwz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53239-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53239 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-05-04 21:54:03 UTC --- s_6 = this_5(D)->children_list_; x.4_39 = (long unsigned int) s_6; D.36426_37 = x.4_39 & 6; I think the code is depending on undefined code dealing with alignment requirements on pointers.
next prev parent reply other threads:[~2012-05-04 21:54 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-04 21:41 [Bug c++/53239] New: " proski at gnu dot org 2012-05-04 21:43 ` [Bug c++/53239] " proski at gnu dot org 2012-05-04 21:54 ` pinskia at gcc dot gnu.org [this message] 2012-05-04 21:55 ` pinskia at gcc dot gnu.org 2012-05-04 22:03 ` [Bug middle-end/53239] [4.7 Regression] VRP vs named value return opt pinskia at gcc dot gnu.org 2012-05-04 23:21 ` hjl.tools at gmail dot com 2012-05-07 3:22 ` proski at gnu dot org 2012-05-07 7:14 ` [Bug tree-optimization/53239] " jakub at gcc dot gnu.org 2012-05-07 7:27 ` jakub at gcc dot gnu.org 2012-05-07 9:35 ` rguenth at gcc dot gnu.org 2012-05-07 9:38 ` rguenth at gcc dot gnu.org 2012-05-07 12:36 ` proski at gnu dot org 2012-05-07 13:24 ` [Bug tree-optimization/53239] [4.7/4.8 " hjl.tools at gmail dot com 2012-05-07 13:33 ` dak at gnu dot org 2012-05-07 13:33 ` jakub at gcc dot gnu.org 2012-05-07 13:34 ` jakub at gcc dot gnu.org 2012-05-16 15:58 ` 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-53239-4-BfYgnQclwz@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).