public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67396] [4.9/5.0 regression] Performance regression compiling variadic function with many arguments
Date: Sun, 30 Aug 2015 16:36:00 -0000	[thread overview]
Message-ID: <bug-67396-4-JfMr15eN2G@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67396-4@http.gcc.gnu.org/bugzilla/>

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

Paul Pluzhnikov <ppluzhnikov at google dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jh at suse dot cz

--- Comment #1 from Paul Pluzhnikov <ppluzhnikov at google dot com> ---
This is "caused" by r206947:

 2014-01-22  Jan Hubicka  <jh@suse.cz>

+       * config/i386/x86-tune.def (X86_TUNE_ACCUMULATE_OUTGOING_ARGS):
+       Enable for generic and recent AMD targets.
+
+2014-01-22  Jan Hubicka  <jh@suse.cz>
+
        * combine-stack-adj.c (combine_stack_adjustments_for_block): Remove
        ARG_SIZE note when adjustment was eliminated.

Index: gcc/config/i386/x86-tune.def
===================================================================
--- gcc/config/i386/x86-tune.def        (revision 206946)
+++ gcc/config/i386/x86-tune.def        (revision 206947)
@@ -146,7 +146,7 @@
    use of the frame pointer in 32bit mode.  */
 DEF_TUNE (X86_TUNE_ACCUMULATE_OUTGOING_ARGS, "accumulate_outgoing_args",
          m_PPRO | m_P4_NOCONA | m_BONNELL | m_SILVERMONT | m_INTEL
-         | m_AMD_MULTIPLE | m_GENERIC)
+         | m_ATHLON_K8)

 /* X86_TUNE_PROLOGUE_USING_MOVE: Do not use push/pop in prologues that are
    considered on critical path.  */



The patch appears to be backwards from what the commit message says though?

$ time gcc-svn-r206948/bin/gcc -c -O2 t.c -mtune=k8

real    0m1.411s
user    0m1.391s
sys     0m0.019s

$ time gcc-svn-r206948/bin/gcc -c -O2 t.c
^C

real    1m31.462s
user    0m0.000s
sys     0m0.006s

$ time gcc-svn-r206948/bin/gcc -c -O2 t.c -mtune=generic
^C

real    1m14.054s
user    0m0.000s
sys     0m0.004s


  reply	other threads:[~2015-08-30 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-29 22:09 [Bug c/67396] New: " ppluzhnikov at google dot com
2015-08-30 16:36 ` ppluzhnikov at google dot com [this message]
2015-08-30 16:53 ` [Bug target/67396] " pinskia at gcc dot gnu.org
2015-08-30 17:14 ` ppluzhnikov at google dot com
2015-08-30 17:23 ` pinskia at gcc dot gnu.org
2015-08-30 18:03 ` ppluzhnikov at google dot com
2015-08-31  8:10 ` [Bug rtl-optimization/67396] [4.9/5/6 regression] Performance regression compiling variadic function with many arguments in RTL DSE rguenth at gcc dot gnu.org
2015-08-31  9:20 ` [Bug rtl-optimization/67396] [4.9/5.0 regression] Performance regression compiling variadic function with many arguments miyuki at gcc dot gnu.org
2015-08-31  9:26 ` [Bug rtl-optimization/67396] [4.9/5/6 regression] Performance regression compiling variadic function with many arguments in RTL DSE miyuki 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-67396-4-JfMr15eN2G@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).