public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/55415] Early SRA produces unaligned complex types Date: Tue, 20 Nov 2012 17:09:00 -0000 [thread overview] Message-ID: <bug-55415-4-TUzvgwhSLQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55415-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55415 --- Comment #1 from Richard Henderson <rth at gcc dot gnu.org> 2012-11-20 17:08:15 UTC --- The call to get_pointer_alignment_1 at ipa-prop.c:2959 does not do what the author intended. In particular we really really need to notice the "false" return value when the results are conservative, and do nothing.
next prev parent reply other threads:[~2012-11-20 17:09 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-20 16:57 [Bug tree-optimization/55415] New: " rth at gcc dot gnu.org 2012-11-20 17:09 ` rth at gcc dot gnu.org [this message] 2012-11-20 20:34 ` [Bug tree-optimization/55415] " jamborm at gcc dot gnu.org 2012-11-23 18:02 ` jakub at gcc dot gnu.org 2012-11-27 20:46 ` jamborm at gcc dot gnu.org 2012-11-30 16:12 ` jamborm at gcc dot gnu.org 2012-12-03 13:28 ` jamborm 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-55415-4-TUzvgwhSLQ@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).