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/59990] [4.8 regression] incorrect memcpy optimization
Date: Wed, 10 Jun 2015 12:53:00 -0000	[thread overview]
Message-ID: <bug-59990-4-r1Eld5HTNz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59990-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59990

--- Comment #24 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Wed Jun 10 12:53:09 2015
New Revision: 224327

URL: https://gcc.gnu.org/viewcvs?rev=224327&root=gcc&view=rev
Log:
2015-06-10  Richard Biener  <rguenther@suse.de>

        Backport from mainline
        2014-04-04  Cong Hou  <congh@google.com>

        PR tree-optimization/60656
        * tree-vect-stmts.c (supportable_widening_operation):
        Fix a bug that elements in a vector with vect_used_by_reduction
        property are incorrectly reordered when the operation on it is not
        consistant with the one in reduction operation.

        * gcc.dg/vect/pr60656.c: New test.

        2014-01-31  Richard Biener  <rguenther@suse.de>

        PR middle-end/59990
        * builtins.c (fold_builtin_memory_op): Make sure to not
        use a floating-point mode or a boolean or enumeral type for
        the copy operation.

        * gcc.dg/torture/pr59990.c: New testcase.
        * gcc.target/i386/pr49168-1.c: Adjust.

Added:
    branches/gcc-4_8-branch/gcc/testsuite/gcc.dg/torture/pr59990.c
    branches/gcc-4_8-branch/gcc/testsuite/gcc.dg/vect/pr60656.c
Modified:
    branches/gcc-4_8-branch/gcc/ChangeLog
    branches/gcc-4_8-branch/gcc/builtins.c
    branches/gcc-4_8-branch/gcc/testsuite/ChangeLog
    branches/gcc-4_8-branch/gcc/testsuite/gcc.target/i386/pr49168-1.c
    branches/gcc-4_8-branch/gcc/tree-vect-stmts.c


  parent reply	other threads:[~2015-06-10 12:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 20:31 [Bug middle-end/59990] New: [4.7/4.8/4.9 " ebotcazou at gcc dot gnu.org
2014-01-29 21:06 ` [Bug middle-end/59990] " joseph at codesourcery dot com
2014-01-29 21:17 ` [Bug target/59990] " pinskia at gcc dot gnu.org
2014-01-29 22:28 ` [Bug middle-end/59990] " ebotcazou at gcc dot gnu.org
2014-01-30  3:45 ` [Bug target/59990] " hjl.tools at gmail dot com
2014-01-30  8:10 ` [Bug middle-end/59990] " ebotcazou at gcc dot gnu.org
2014-01-30  8:15 ` jakub at gcc dot gnu.org
2014-01-30  8:31 ` ebotcazou at gcc dot gnu.org
2014-01-30 12:08 ` rguenth at gcc dot gnu.org
2014-01-30 12:49 ` rguenth at gcc dot gnu.org
2014-01-30 12:53 ` rguenth at gcc dot gnu.org
2014-01-30 13:15 ` jakub at gcc dot gnu.org
2014-01-30 16:43 ` joseph at codesourcery dot com
2014-01-30 17:38 ` jakub at gcc dot gnu.org
2014-01-31 11:39 ` rguenth at gcc dot gnu.org
2014-01-31 11:55 ` [Bug middle-end/59990] [4.7/4.8 " rguenth at gcc dot gnu.org
2014-01-31 11:55 ` [Bug middle-end/59990] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org
2014-01-31 11:55 ` [Bug middle-end/59990] [4.7/4.8 " rguenth at gcc dot gnu.org
2014-02-10 15:25 ` rguenth at gcc dot gnu.org
2014-02-10 15:29 ` rguenth at gcc dot gnu.org
2014-06-12 13:46 ` rguenth at gcc dot gnu.org
2014-12-19 13:29 ` [Bug middle-end/59990] [4.8 " jakub at gcc dot gnu.org
2015-02-16 13:19 ` anders.blomdell at control dot lth.se
2015-02-16 13:20 ` anders.blomdell at control dot lth.se
2015-02-16 13:23 ` anders.blomdell at control dot lth.se
2015-02-16 13:25 ` anders.blomdell at control dot lth.se
2015-02-16 13:26 ` anders.blomdell at control dot lth.se
2015-06-10 12:53 ` rguenth at gcc dot gnu.org [this message]
2015-06-10 13:51 ` rguenth 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-59990-4-r1Eld5HTNz@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: link
Be 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).