public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/26134] New: fold *(float*)(&complex_float_var) into REALPART_EXPR<complex_float_var> Date: Mon, 06 Feb 2006 16:58:00 -0000 [thread overview] Message-ID: <bug-26134-6528@http.gcc.gnu.org/bugzilla/> (raw) I was looking at some code which is mentioned to be in SPEC 2006 (I forgot where I found the mentioning) but anyways it has the following in it: typedef _Complex float COMPLEX_FLOAT; float real_part(COMPLEX_FLOAT a) { return *(float*)(&a); } This should be converted to: float real_part(COMPLEX_FLOAT a) { return __real__ a; } So that the tree optimizers can work on it easier. -- Summary: fold *(float*)(&complex_float_var) into REALPART_EXPR<complex_float_var> Product: gcc Version: 4.2.0 Status: UNCONFIRMED Keywords: missed-optimization, TREE Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26134
next reply other threads:[~2006-02-06 16:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-06 16:58 pinskia at gcc dot gnu dot org [this message] 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-6528@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).