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: Wed, 22 Dec 2010 12:57:00 -0000 [thread overview]
Message-ID: <bug-45934-4-czoqkUOML0@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 #8 from Martin Jambor <jamborm at gcc dot gnu.org> 2010-12-22 12:57:00 UTC ---
Author: jamborm
Date: Wed Dec 22 12:56:54 2010
New Revision: 168168
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168168
Log:
2010-12-22 Martin Jambor <mjambor@suse.cz>
PR tree-optimization/45934
PR tree-optimization/46302
PR tree-optimization/46987
* gimple-fold.c (get_base_binfo_for_type): Removed.
(gimple_get_relevant_ref_binfo): Likewise.
(gimple_fold_obj_type_ref_call): Dumb down to 4.5 functionality,
removed parameter inplace, updated the caller.
* gimple.h (gimple_get_relevant_ref_binfo): Remove declaration.
* ipa-cp.c (ipcp_propagate_types): Do not derive types from constants.
(ipcp_discover_new_direct_edges): Do not do devirtualization based on
constants.
* ipa-prop.c (compute_known_type_jump_func): Use
get_ref_base_and_extent and get_binfo_at_offset instead of
gimple_get_relevant_ref_binfo.
(compute_known_type_jump_func): Likewise.
(update_jump_functions_after_inlining): Do not derive types from
constants.
(try_make_edge_direct_virtual_call): Likewise.
* tree.c (get_binfo_at_offset): Get type from non-artificial fields.
* testsuite/g++.dg/ipa/ipcp-ivi-1.C: Removed.
* testsuite/g++.dg/ipa/ivinline-6.C: Likewise.
* testsuite/g++.dg/otr-fold-1.C: Likewise.
* testsuite/g++.dg/otr-fold-2.C: Likewise.
* testsuite/g++.dg/tree-ssa/pr43411.C: Xfail dump scan.
* testsuite/g++.dg/tree-ssa/pr45605.C: Likewise.
* testsuite/g++.dg/tree-ssa/pr46987.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/tree-ssa/pr46987.C
Removed:
trunk/gcc/testsuite/g++.dg/ipa/ipcp-ivi-1.C
trunk/gcc/testsuite/g++.dg/ipa/ivinline-6.C
trunk/gcc/testsuite/g++.dg/otr-fold-1.C
trunk/gcc/testsuite/g++.dg/otr-fold-2.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/gimple-fold.c
trunk/gcc/gimple.h
trunk/gcc/ipa-cp.c
trunk/gcc/ipa-prop.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/tree-ssa/pr43411.C
trunk/gcc/testsuite/g++.dg/tree-ssa/pr45605.C
trunk/gcc/tree.c
next prev parent reply other threads:[~2010-12-22 12:57 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 [this message]
2010-12-29 8:45 ` jamborm at gcc dot gnu.org
2011-01-14 23:54 ` jamborm at gcc dot gnu.org
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-czoqkUOML0@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).