public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45934] [4.6 Regression] g++.old-deja/g++.other/dtor5.C FAILs with -finline-small-functions
Date: Fri, 14 Jan 2011 23:54:00 -0000	[thread overview]
Message-ID: <bug-45934-4-v4LA3OYIBj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45934-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Martin Jambor <jamborm at gcc dot gnu.org> 2011-01-14 23:01:02 UTC ---
Author: jamborm
Date: Fri Jan 14 23:00:59 2011
New Revision: 168825

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168825
Log:
2011-01-14  Martin Jambor  <mjambor@suse.cz>

    PR tree-optimization/45934
    PR tree-optimization/46302
    * ipa-prop.c (type_change_info): New type.
    (stmt_may_be_vtbl_ptr_store): New function.
    (check_stmt_for_type_change): Likewise.
    (detect_type_change): Likewise.
    (detect_type_change_ssa): Likewise.
    (compute_complex_assign_jump_func): Check for dynamic type change.
    (compute_complex_ancestor_jump_func): Likewise.
    (compute_known_type_jump_func): Likewise.
    (compute_scalar_jump_functions): Likewise.
    (ipa_analyze_virtual_call_uses): Likewise.
    (ipa_analyze_node): Push and pop cfun, set current_function_decl.

    * testsuite/g++.dg/ipa/devirt-c-1.C: New test.
    * testsuite/g++.dg/ipa/devirt-c-2.C: Likewise.
    * testsuite/g++.dg/ipa/devirt-c-3.C: Likewise.
    * testsuite/g++.dg/ipa/devirt-c-4.C: Likewise.
    * testsuite/g++.dg/ipa/devirt-c-5.C: Likewise.
    * testsuite/g++.dg/ipa/devirt-c-6.C: Likewise.
    * testsuite/g++.dg/ipa/devirt-6.C: Likewise.
    * testsuite/g++.dg/ipa/devirt-d-1.C: Likewise.
    * testsuite/g++.dg/torture/pr45934.C: Likewise.


Added:
    trunk/gcc/testsuite/g++.dg/ipa/devirt-6.C
    trunk/gcc/testsuite/g++.dg/ipa/devirt-c-1.C
    trunk/gcc/testsuite/g++.dg/ipa/devirt-c-2.C
    trunk/gcc/testsuite/g++.dg/ipa/devirt-c-3.C
    trunk/gcc/testsuite/g++.dg/ipa/devirt-c-4.C
    trunk/gcc/testsuite/g++.dg/ipa/devirt-c-5.C
    trunk/gcc/testsuite/g++.dg/ipa/devirt-c-6.C
    trunk/gcc/testsuite/g++.dg/ipa/devirt-d-1.C
    trunk/gcc/testsuite/g++.dg/torture/pr45934.C
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/ipa-prop.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2011-01-14 23:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 13:22 [Bug tree-optimization/45934] New: " zsojka at seznam dot cz
2010-10-07 13:56 ` [Bug tree-optimization/45934] " rguenth at gcc dot gnu.org
2010-10-07 13:58 ` rguenth at gcc dot gnu.org
2010-10-07 16:17 ` jason at gcc dot gnu.org
2010-10-26  4:03 ` jakub at gcc dot gnu.org
2010-11-12 18:23 ` jamborm at gcc dot gnu.org
2010-11-22 22:43 ` jamborm at gcc dot gnu.org
2010-12-16 15:30 ` jamborm at gcc dot gnu.org
2010-12-22 12:57 ` jamborm at gcc dot gnu.org
2010-12-29  8:45 ` jamborm at gcc dot gnu.org
2011-01-14 23:54 ` jamborm at gcc dot gnu.org [this message]
2011-01-15 16:51 ` hubicka at gcc dot gnu.org
2011-01-17 14:50 ` jamborm 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-45934-4-v4LA3OYIBj@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).