public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/53663] [4.7/4.8 Regression] inconsistent inline handling of bool within union Date: Mon, 24 Sep 2012 09:15:00 -0000 [thread overview] Message-ID: <bug-53663-4-w17oe3bhuS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53663-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53663 --- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-09-24 09:14:31 UTC --- Guess for BOOLEAN_TYPE in unions we can't look just at the single bit, but also all other bits of the boolean type, because we rely that the bool doesn't contain other values than false/true.
next prev parent reply other threads:[~2012-09-24 9:15 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-13 22:47 [Bug c/53663] New: 4.7 " brendan.jones.it at gmail dot com 2012-06-13 23:20 ` [Bug tree-optimization/53663] " pinskia at gcc dot gnu.org 2012-06-14 8:41 ` rguenth at gcc dot gnu.org 2012-06-14 9:01 ` brendan.jones.it at gmail dot com 2012-06-24 7:57 ` brendan.jones.it at gmail dot com 2012-09-23 10:01 ` fdziarmagowski at gmail dot com 2012-09-23 11:57 ` mikpe at it dot uu.se 2012-09-23 17:14 ` mikpe at it dot uu.se 2012-09-23 18:45 ` mikpe at it dot uu.se 2012-09-23 19:52 ` fdziarmagowski at gmail dot com 2012-09-23 22:12 ` mikpe at it dot uu.se 2012-09-24 7:18 ` [Bug tree-optimization/53663] [4.7/4.8 Regression] " jakub at gcc dot gnu.org 2012-09-24 9:08 ` rguenth at gcc dot gnu.org 2012-09-24 9:15 ` jakub at gcc dot gnu.org [this message] 2012-09-24 11:45 ` rguenth at gcc dot gnu.org 2012-09-24 13:14 ` rguenth at gcc dot gnu.org 2012-09-25 7:52 ` rguenth at gcc dot gnu.org 2012-09-25 7:55 ` [Bug tree-optimization/53663] [4.7 " rguenth at gcc dot gnu.org 2012-09-25 8:31 ` fdziarmagowski at gmail dot com 2012-12-03 15:34 ` rguenth at gcc dot gnu.org 2012-12-03 16:54 ` rguenth at gcc dot gnu.org 2012-12-03 16:54 ` rguenth 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-53663-4-w17oe3bhuS@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).