public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/26439] New: [4.2 Regression] missing VOPs for complex assignments Date: Thu, 23 Feb 2006 12:13:00 -0000 [thread overview] Message-ID: <bug-26439-10053@http.gcc.gnu.org/bugzilla/> (raw) _Complex double c; _Complex double foo(void) { _Complex double *cp = &c; __real c = __imag c; return *cp; } has in alias1: foo () { complex double * cp; complex double D.1527; double D.1526; <bb 2>: cp_1 = &c; # VUSE <SFT.0_2>; D.1526_3 = IMAGPART_EXPR <c>; # SFT.1_5 = V_MUST_DEF <SFT.1_4>; REALPART_EXPR <c> = D.1526_3; # VUSE <SFT.1_5>; D.1527_6 = *cp_1; # <retval>_8 = V_MUST_DEF <<retval>_7>; <retval> = D.1527_6; # VUSE <<retval>_8>; return <retval>; } note how D.1527_6 = *cp_1; misses VUSE <SFT.0_2> -- Summary: [4.2 Regression] missing VOPs for complex assignments Product: gcc Version: 4.2.0 Status: UNCONFIRMED Keywords: wrong-code, alias Severity: critical Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rguenth at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26439
next reply other threads:[~2006-02-23 12:13 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-23 12:13 rguenth at gcc dot gnu dot org [this message] 2006-02-23 12:20 ` [Bug middle-end/26439] " rguenth at gcc dot gnu dot org 2006-02-23 16:03 ` rguenth at gcc dot gnu dot org 2006-02-23 16:16 ` rguenth at gcc dot gnu dot org 2006-02-24 17:32 ` pinskia at gcc dot gnu dot org 2006-02-24 17:34 ` pinskia at gcc dot gnu dot org 2006-02-24 17:36 ` pinskia at gcc dot gnu dot org 2006-02-24 17:38 ` pinskia at gcc dot gnu dot org 2006-02-24 17:47 ` pinskia at gcc dot gnu dot org 2006-02-24 18:23 ` 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-26439-10053@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).