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 middle-end/26134] fold *(float*)(&complex_float_var) into REALPART_EXPR<complex_float_var> Date: Wed, 16 Mar 2011 13:57:00 -0000 [thread overview] Message-ID: <bug-26134-4-XE2XWMCc7c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-26134-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26134 --- Comment #9 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-16 13:53:17 UTC --- Author: rguenth Date: Wed Mar 16 13:53:09 2011 New Revision: 171046 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=171046 Log: 2011-03-16 Richard Guenther <rguenther@suse.de> PR tree-optimization/26134 * tree-ssa.c (maybe_rewrite_mem_ref_base): Handle rewriting complex part accesses to REALPART_EXPR and IMAGPART_EXPR. (non_rewritable_mem_ref_base): Handle complex type component accesses, constrain offsets for vector and complex extracts more properly. * gcc.dg/tree-ssa/complex-6.c: New testcase. Added: trunk/gcc/testsuite/gcc.dg/tree-ssa/complex-6.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-ssa.c
next parent reply other threads:[~2011-03-16 13:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-26134-4@http.gcc.gnu.org/bugzilla/> 2011-03-16 13:57 ` rguenth at gcc dot gnu.org [this message] 2006-02-06 16:58 [Bug middle-end/26134] New: " pinskia at gcc dot gnu dot org 2006-02-06 16:58 ` [Bug middle-end/26134] " pinskia at gcc dot gnu dot org 2006-02-06 17:45 ` pinskia at gcc dot gnu dot org 2006-02-07 15:49 ` pinskia at gcc dot gnu dot org 2006-02-07 18:47 ` pluto at agmk dot net 2006-02-07 18:52 ` pinskia at gcc dot gnu dot org 2006-02-07 18:56 ` falk at debian dot org 2006-02-09 14:14 ` pinskia at gcc dot gnu dot org 2006-02-09 14:15 ` pinskia at gcc dot gnu dot 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-26134-4-XE2XWMCc7c@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).