public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dushistov at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/57890] gcc 4.8.1 regression: loops become slower
Date: Sat, 13 Jul 2013 16:39:00 -0000	[thread overview]
Message-ID: <bug-57890-4-9VTmLLJFHV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57890-4@http.gcc.gnu.org/bugzilla/>

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

Evgeniy Dushistov <dushistov at mail dot ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|target                      |tree-optimization

--- Comment #2 from Evgeniy Dushistov <dushistov at mail dot ru> ---
>That would mean the expansion for memset is not optimal for the target which >means this is a target issue rather than a C++ front-end or a middle-end issue.

I disagree. Bisect show that fault commit (Can anybody add him to CC?):
  2012-06-05  Richard Guenther  <rguenther@suse.de>

        PR tree-optimization/53081
        * tree-loop-distribution.c (generate_memset_builtin): Handle all
        kinds of byte-sized stores.
        (classify_partition): Likewise.
        (tree_loop_distribution): Adjust seed statements used for
        !flag_tree_loop_distribution.

        * gcc.dg/tree-ssa/ldist-19.c: New testcase.
        * gcc.c-torture/execute/builtins/builtins.exp: Always pass
        -fno-tree-loop-distribute-patterns.

Yes, for builtin memset gcc generated bad code, and this a target issue.

But for gcc 4.7 the issue was known
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55953), that bultin memset bad for
at least arm, x86 and amd64 ( suppose major CPUs that gcc supports).

Why in gcc 4.8 introduce new code in tree optimization that produce more builin
memset, why not wait untill builtin memset will be fixed?

If look at gcc as the whole thing, this is regression: "+15% CPU time for
simple loop".


  parent reply	other threads:[~2013-07-13 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-57890-4@http.gcc.gnu.org/bugzilla/>
2013-07-12 17:14 ` [Bug target/57890] " pinskia at gcc dot gnu.org
2013-07-13 16:39 ` dushistov at mail dot ru [this message]
2013-07-14 19:46 ` [Bug tree-optimization/57890] " dushistov at mail dot ru
2013-11-09 22:34 ` [Bug target/57890] " pinskia at gcc dot gnu.org
2013-11-09 23:36 ` pinskia at gcc dot gnu.org
2021-06-08 21:37 ` pinskia 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-57890-4-9VTmLLJFHV@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).