public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vbyakovl23 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/53726] New: [4.8 Regression] aes test performance drop for eembc_2_0_peak_32
Date: Wed, 20 Jun 2012 06:10:00 -0000	[thread overview]
Message-ID: <bug-53726-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53726

             Bug #: 53726
           Summary: [4.8 Regression] aes test performance drop for
                    eembc_2_0_peak_32
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: vbyakovl23@gmail.com


After fix

r188261 | rguenth | 2012-06-06 13:45:27 +0400 (Wed, 06 Jun 2012) | 23 lines

2012-06-06  Richard Guenther  <rguenther@suse.de>

        PR tree-optimization/53081
        * tree-data-ref.h (adjacent_store_dr_p): Rename to ...
        (adjacent_dr_p): ... this and make it work for reads, too.
        * tree-loop-distribution.c (enum partition_kind): Add PKIND_MEMCPY.
        (struct partition_s): Change main_stmt to main_dr, add
        secondary_dr member.
        (build_size_arg_loc): Change to date data-reference and not
        gimplify here.
        (build_addr_arg_loc): New function split out from ...
        (generate_memset_builtin): ... here.  Use it and simplify.
        (generate_memcpy_builtin): New function.
        (generate_code_for_partition): Adjust.
        (classify_partition): Streamline pattern detection.  Detect
        memcpy.
        (ldist_gen): Adjust.
        (tree_loop_distribution): Adjust seed statements for memcpy
        recognition.

        * gcc.dg/tree-ssa/ldist-20.c: New testcase.
        * gcc.dg/tree-ssa/loop-19.c: Add -fno-tree-loop-distribute-patterns.

regression on Atom 11%, on Sundy Bridge 30%. The fix lead to unrecognition of
memcpy. Reduced test case and assemblers are attached. Command line to
reproduce

gcc -ansi -O3 -ffast-math -msse2 -mfpmath=sse -m32 -static  -march=corei7
-mtune=corei7   test.c


             reply	other threads:[~2012-06-20  6:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20  6:10 vbyakovl23 at gmail dot com [this message]
2012-06-20  6:13 ` [Bug c/53726] " vbyakovl23 at gmail dot com
2012-06-20  9:28 ` [Bug tree-optimization/53726] " rguenth at gcc dot gnu.org
2012-06-20 10:48 ` vbyakovl23 at gmail dot com
2012-06-20 10:50 ` vbyakovl23 at gmail dot com
2012-06-20 11:48 ` rguenth at gcc dot gnu.org
2012-06-20 12:31 ` rguenth at gcc dot gnu.org
2012-06-20 12:47 ` hjl.tools at gmail dot com
2012-06-20 13:30 ` rguenther at suse dot de
2012-06-20 14:20 ` hjl.tools at gmail dot com
2012-06-20 14:35 ` vbyakovl23 at gmail dot com
2012-06-20 14:36 ` rguenth at gcc dot gnu.org
2012-06-20 14:44 ` hjl.tools at gmail dot com
2012-06-20 14:47 ` hjl.tools at gmail dot com
2012-06-20 14:52 ` hjl.tools at gmail dot com
2012-06-20 14:55 ` rguenther at suse dot de
2012-06-20 15:10 ` rguenth at gcc dot gnu.org
2012-06-20 15:37 ` hjl.tools at gmail dot com
2012-06-21  8:47 ` rguenther at suse dot de
2012-06-21 12:47 ` vbyakovl23 at gmail dot com
2012-06-21 12:51 ` hjl.tools at gmail dot com
2012-06-21 12:56 ` hjl.tools at gmail dot com
2012-06-22 22:46 ` hubicka at ucw dot cz
2012-06-22 23:04   ` Jan Hubicka
2012-06-22 23:05 ` hubicka at ucw dot cz

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-53726-4@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).