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/65215] [5 Regression] Bswap load miscompilation Date: Thu, 26 Feb 2015 22:50:00 -0000 [thread overview] Message-ID: <bug-65215-4-jCkZYZe5vA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65215-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65215 --- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Thu Feb 26 21:01:59 2015 New Revision: 221033 URL: https://gcc.gnu.org/viewcvs?rev=221033&root=gcc&view=rev Log: PR tree-optimization/65215 * tree-ssa-math-opts.c (find_bswap_or_nop_load): Return false for PDP endian targets. (perform_symbolic_merge, find_bswap_or_nop_1, find_bswap_or_nop): Fix up formatting issues. (bswap_replace): Likewise. For BYTES_BIG_ENDIAN, if the final access size is smaller than the original, adjust MEM_REF offset by the difference of sizes. Use is_gimple_mem_ref_addr instead of is_gimple_min_invariant test to avoid adding address temporaries. * gcc.c-torture/execute/pr65215-1.c: New test. * gcc.c-torture/execute/pr65215-2.c: New test. * gcc.c-torture/execute/pr65215-3.c: New test. * gcc.c-torture/execute/pr65215-4.c: New test. * gcc.c-torture/execute/pr65215-5.c: New test. Added: trunk/gcc/testsuite/gcc.c-torture/execute/pr65215-1.c trunk/gcc/testsuite/gcc.c-torture/execute/pr65215-2.c trunk/gcc/testsuite/gcc.c-torture/execute/pr65215-3.c trunk/gcc/testsuite/gcc.c-torture/execute/pr65215-4.c trunk/gcc/testsuite/gcc.c-torture/execute/pr65215-5.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-ssa-math-opts.c
next prev parent reply other threads:[~2015-02-26 21:02 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-26 0:27 [Bug tree-optimization/65215] New: " jakub at gcc dot gnu.org 2015-02-26 0:44 ` [Bug tree-optimization/65215] " jakub at gcc dot gnu.org 2015-02-26 11:07 ` jakub at gcc dot gnu.org 2015-02-26 11:17 ` jakub at gcc dot gnu.org 2015-02-26 11:32 ` jakub at gcc dot gnu.org 2015-02-26 11:36 ` rguenth at gcc dot gnu.org 2015-02-26 11:45 ` thopre01 at gcc dot gnu.org 2015-02-26 11:45 ` jakub at gcc dot gnu.org 2015-02-26 12:28 ` thopre01 at gcc dot gnu.org 2015-02-26 12:37 ` jakub at gcc dot gnu.org 2015-02-26 12:39 ` rguenth at gcc dot gnu.org 2015-02-26 12:46 ` rguenth at gcc dot gnu.org 2015-02-26 22:50 ` jakub at gcc dot gnu.org [this message] 2015-02-27 0:21 ` 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-65215-4-jCkZYZe5vA@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).