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 tree-optimization/65077] [4.9/5 Regression] memcpy generates incorrect code with floating point numbers and -O1 Date: Mon, 16 Feb 2015 13:51:00 -0000 [thread overview] Message-ID: <bug-65077-4-XIrLUtli1P@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65077-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65077 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Status|REOPENED |ASSIGNED Component|c |tree-optimization Known to work| |4.8.2 Target Milestone|--- |4.9.3 Summary|memcpy generates incorrect |[4.9/5 Regression] memcpy |code with floating point |generates incorrect code |numbers and -O1 |with floating point numbers | |and -O1 --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- The if (FLOAT_TYPE_P (TREE_TYPE (lhsop))) /* If the operation produces a floating point result then assume the value is not produced to transfer a pointer. */ ; case is new in 4.9 (4.8 didn't have it - doing this improves points-to results for scientific benchmarks which have both pointers and FP values in aggregates). Changed by r197158: 2013-03-27 Richard Biener <rguenther@suse.de> PR tree-optimization/37021 * tree-vect-data-refs.c (vect_check_strided_load): Allow REALPART/IMAGPART_EXPRs around the supported refs. * tree-ssa-structalias.c (find_func_aliases): Assume that floating-point values are not used to transfer pointers.
next prev parent reply other threads:[~2015-02-16 13:51 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-16 13:18 [Bug c/65077] New: " anders.blomdell at control dot lth.se 2015-02-16 13:25 ` [Bug c/65077] " rguenth at gcc dot gnu.org 2015-02-16 13:27 ` anders.blomdell at control dot lth.se 2015-02-16 13:28 ` anders.blomdell at control dot lth.se 2015-02-16 13:36 ` rguenth at gcc dot gnu.org 2015-02-16 13:40 ` anders.blomdell at control dot lth.se 2015-02-16 13:46 ` rguenth at gcc dot gnu.org 2015-02-16 13:51 ` rguenth at gcc dot gnu.org [this message] 2015-02-16 13:58 ` [Bug tree-optimization/65077] [4.9/5 Regression] " anders.blomdell at control dot lth.se 2015-02-16 14:01 ` anders.blomdell at control dot lth.se 2015-02-16 14:15 ` rguenth at gcc dot gnu.org 2015-02-16 18:11 ` anders.blomdell at control dot lth.se 2015-02-16 18:12 ` anders.blomdell at control dot lth.se 2015-02-16 18:15 ` [Bug tree-optimization/65077] [4.9 " rguenth at gcc dot gnu.org 2015-02-16 18:15 ` rguenth at gcc dot gnu.org 2015-02-16 18:25 ` anders.blomdell at control dot lth.se 2015-02-17 9:52 ` rguenther at suse dot de 2015-05-11 10:50 ` rguenth at gcc dot gnu.org 2015-06-26 20:10 ` jakub at gcc dot gnu.org 2015-06-26 20:36 ` 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-65077-4-XIrLUtli1P@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).