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/47239] [4.6 Regression] (int)&func & 3 is always optimized to 0 on some targets Date: Tue, 11 Jan 2011 13:03:00 -0000 [thread overview] Message-ID: <bug-47239-4-554wFFbkQF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47239-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47239 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2011.01.11 12:53:34 AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org |gnu.org | Target Milestone|--- |4.6.0 Summary|(int)&func & 3 is always |[4.6 Regression] (int)&func |optimized to 0 on some |& 3 is always optimized to |targets |0 on some targets Ever Confirmed|0 |1 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-01-11 12:53:34 UTC --- Confirmed, mine. The fix for PR35705 only extracts alignment information from function decls for the single case &fn & 1. That's odd. I'm going to simply punt for function-decls for now.
next prev parent reply other threads:[~2011-01-11 12:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-10 0:01 [Bug tree-optimization/47239] New: " kkojima at gcc dot gnu.org 2011-01-11 13:03 ` rguenth at gcc dot gnu.org [this message] 2011-01-11 14:33 ` [Bug tree-optimization/47239] [4.6 Regression] " rguenth at gcc dot gnu.org 2011-01-11 23:17 ` kkojima at gcc dot gnu.org 2011-01-12 13:10 ` 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-47239-4-554wFFbkQF@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).