public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/65076] [5 Regression] 16% tramp3d-v4.cpp compile time regression
Date: Tue, 31 Mar 2015 17:53:00 -0000	[thread overview]
Message-ID: <bug-65076-4-lsGFDZpSvW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65076-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #42 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Sorry, accidental message.

It is 69->80.5s between 141127.61083 and 150113.26056 (tester was down)
      66->69s between 141123.15275 and 141124.01653
      60->64 between 140807.80282 and 140808.66762

Now the other tester shows 
      59->50 between 150112.41636 and 150113.13858
      51->53 between 141124.14999 and 141123.43031
      45->48 between 140807.01584 and 140808.72560

Can we, please, restart the frescobaldi tester? It is down sine 23rd.

There is an inline change
2015-01-12  Jan Hubicka  <hubicka@ucw.cz>

        PR ipa/63967
        PR ipa/64425
        * ipa-inline.c (compute_uninlined_call_time,
        compute_inlined_call_time): Use counts for extra precision when
        needed possible.
        (big_speedup_p): Fix formating.
        (RELATIVE_TIME_BENEFIT_RANGE): Remove.
        (relative_time_benefit): Remove.
        (edge_badness): Turn DECL_DISREGARD_INLINE_LIMITS into hint;
        merge guessed and read profile paths.
        (inline_small_functions): Count only !optimize_size functions into
        initial size; be more lax about sanity check when profile is used;
        be sure to update inlined function profile when profile is read.

2015-01-12  Jan Hubicka  <hubicka@ucw.cz>

        PR ipa/63470
        * ipa-inline-analysis.c (inline_edge_duplication_hook): Adjust
        cost when edge becomes direct.
        * ipa-prop.c (make_edge_direct): Do not adjust when speculation
        is resolved or when introducing new speculation.

2014-11-22  Jan Hubicka  <hubicka@ucw.cz>

        PR ipa/63671
        * ipa-inline-transform.c (can_remove_node_now_p_1): Handle alises
        and -fno-devirtualize more carefully.
        (can_remove_node_now_p): Update.

(it really is 24th)

2014-08-07  Jan Hubicka  <hubicka@ucw.cz>

        * ipa-devirt.c: Include gimple-pretty-print.h
        (referenced_from_vtable_p): Exclude DECL_EXTERNAL from
        further tests.
        (decl_maybe_in_construction_p): Fix conditional on cdtor check
        (get_polymorphic_call_info): Fix return value
        (type_change_info): New sturcture based on ipa-prop
        variant.
        (noncall_stmt_may_be_vtbl_ptr_store): New predicate
        based on ipa-prop variant.
        (extr_type_from_vtbl_ptr_store): New function
        based on ipa-prop variant.
        (record_known_type): New function.
        (check_stmt_for_type_change): New function.
        (get_dynamic_type): New function.
        * ipa-prop.c (ipa_analyze_call_uses): Use get_dynamic_type.
        * tree-ssa-pre.c: ipa-utils.h
        (eliminate_dom_walker::before_dom_children): Use ipa-devirt
        machinery; sanity check with ipa-prop devirtualization.
        * trans-mem.c (ipa_tm_insert_gettmclone_call): Clear
        polymorphic flag.

Last one is ipa-cp change or perhaps get_dynamic_type is expensive (it has some
chance for that). I will add timevar for it.

The first two changes are not what I would expect. Perhaps checking these is a
good idea.  It may be something else comitted the same day.


  parent reply	other threads:[~2015-03-31 17:29 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 13:00 [Bug ipa/65076] New: " trippels at gcc dot gnu.org
2015-02-16 13:14 ` [Bug ipa/65076] " rguenth at gcc dot gnu.org
2015-02-16 13:22 ` trippels at gcc dot gnu.org
2015-02-16 18:31 ` hubicka at gcc dot gnu.org
2015-02-16 19:07 ` trippels at gcc dot gnu.org
2015-02-16 19:15 ` trippels at gcc dot gnu.org
2015-02-17 10:49 ` rguenth at gcc dot gnu.org
2015-03-04  9:10 ` rguenth at gcc dot gnu.org
2015-03-18 12:56 ` rguenth at gcc dot gnu.org
2015-03-21  5:32 ` hubicka at gcc dot gnu.org
2015-03-21 10:25 ` hubicka at gcc dot gnu.org
2015-03-21 10:48 ` hubicka at gcc dot gnu.org
2015-03-21 11:32 ` hubicka at gcc dot gnu.org
2015-03-24 14:56 ` rguenth at gcc dot gnu.org
2015-03-24 17:21 ` jakub at gcc dot gnu.org
2015-03-25  8:42 ` hubicka at ucw dot cz
2015-03-25  8:42 ` hubicka at gcc dot gnu.org
2015-03-25  8:50 ` rguenther at suse dot de
2015-03-25 21:35 ` hubicka at gcc dot gnu.org
2015-03-26  3:23 ` hubicka at gcc dot gnu.org
2015-03-27  4:03 ` hubicka at gcc dot gnu.org
2015-03-27  6:21 ` hubicka at gcc dot gnu.org
2015-03-27  9:34 ` rguenth at gcc dot gnu.org
2015-03-28 22:17 ` hubicka at gcc dot gnu.org
2015-03-29 14:29 ` trippels at gcc dot gnu.org
2015-03-30  6:03 ` hubicka at gcc dot gnu.org
2015-03-30  6:15 ` hubicka at gcc dot gnu.org
2015-03-31 13:03 ` rguenth at gcc dot gnu.org
2015-03-31 13:09 ` trippels at gcc dot gnu.org
2015-03-31 14:10 ` rguenther at suse dot de
2015-03-31 14:13 ` trippels at gcc dot gnu.org
2015-03-31 14:47 ` trippels at gcc dot gnu.org
2015-03-31 15:08 ` trippels at gcc dot gnu.org
2015-03-31 15:10 ` evstupac at gmail dot com
2015-03-31 15:29 ` rguenth at gcc dot gnu.org
2015-03-31 16:06 ` hubicka at ucw dot cz
2015-03-31 16:25 ` hubicka at gcc dot gnu.org
2015-03-31 17:36 ` hubicka at gcc dot gnu.org
2015-03-31 17:53 ` hubicka at gcc dot gnu.org [this message]
2015-03-31 17:54 ` hubicka at gcc dot gnu.org
2015-03-31 20:31 ` trippels at gcc dot gnu.org
2015-04-01  8:02 ` rguenther at suse dot de
2015-04-01  8:05 ` rguenther at suse dot de
2015-04-01  8:28 ` hubicka at gcc dot gnu.org
2015-04-01  8:34 ` trippels at gcc dot gnu.org
2015-04-02  5:18 ` hubicka at gcc dot gnu.org
2015-04-02  7:07 ` hubicka at gcc dot gnu.org
2015-04-02 23:44 ` hubicka at gcc dot gnu.org
2015-04-03 18:09 ` hubicka at gcc dot gnu.org
2015-04-07  9:32 ` rguenth at gcc dot gnu.org
2015-04-22  1:32 ` [Bug ipa/65076] [5/6 " hubicka at gcc dot gnu.org
2015-04-22 12:06 ` jakub at gcc dot gnu.org
2015-07-16  9:19 ` 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-65076-4-lsGFDZpSvW@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).