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 debug/47106] -fcompare-debug failure (length) with  -fpartial-inlining -flto -fconserve-stack
Date: Thu, 17 Feb 2011 16:24:00 -0000	[thread overview]
Message-ID: <bug-47106-4-C0MHHzp4nh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47106-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from Jan Hubicka <hubicka at gcc dot gnu.org> 2011-02-17 16:18:34 UTC ---
Author: hubicka
Date: Thu Feb 17 16:18:24 2011
New Revision: 170249

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=170249
Log:

    PR debug/47106
    PR debug/47402
    * cfgexpand.c (account_used_vars_for_block): Remove.
    (estimated_stack_frame_size): Use referenced vars.
    * tree-inline.c (remap_decl): Only mark VAR_DECLs as referenced
    that were referenced in the original function.  Test src_fn
    rather than cfun.  Drop redundant get_var_ann.
    (setup_one_parameter): Drop redundant get_var_ann.
    (declare_return_variable): Likewise.
    (copy_decl_for_dup_finish): Mark VAR_DECLs referenced in src_fn.
    (copy_arguments_for_versioning): Drop redundant get_var_ann.
    * ipa-inline.c (compute_inline_parameters): Do not compute
    disregard_inline_limits here.
    are not available.
    (compute_inlinable_for_current, pass_inlinable): New.
    (pass_inline_parameters): Require PROP_referenced_vars.
    * cgraphunit.c (cgraph_process_new_functions): Don't run
    compute_inline_parameters explicitly unless function is in
    SSA form.
    (cgraph_analyze_function): Set .disregard_inline_limits.
    * tree-sra.c (convert_callers): Compute inliner parameters
    only for functions already in SSA form.
    * g++.dg/debug/pr47106.C: New.

Added:
    trunk/gcc/testsuite/g++.dg/debug/pr47106.C
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/cfgexpand.c
    trunk/gcc/cgraphunit.c
    trunk/gcc/ipa-inline.c
    trunk/gcc/passes.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-inline.c
    trunk/gcc/tree-sra.c


  parent reply	other threads:[~2011-02-17 16:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29 11:41 [Bug debug/47106] New: " zsojka at seznam dot cz
2010-12-30 20:09 ` [Bug debug/47106] " aoliva at gcc dot gnu.org
2010-12-30 20:15 ` aoliva at gcc dot gnu.org
2011-01-21 15:17 ` aoliva at gcc dot gnu.org
2011-01-21 15:40 ` aoliva at gcc dot gnu.org
2011-01-21 22:36 ` aoliva at gcc dot gnu.org
2011-01-31  8:07 ` aoliva at gcc dot gnu.org
2011-01-31 11:55 ` aoliva at gcc dot gnu.org
2011-02-02  5:44 ` aoliva at gcc dot gnu.org
2011-02-02  6:18 ` aoliva at gcc dot gnu.org
2011-02-02  6:28 ` aoliva at gcc dot gnu.org
2011-02-15 18:36 ` aoliva at gcc dot gnu.org
2011-02-15 18:37 ` aoliva at gcc dot gnu.org
2011-02-15 18:37 ` aoliva at gcc dot gnu.org
2011-02-15 18:38 ` aoliva at gcc dot gnu.org
2011-02-17 16:24 ` hubicka at gcc dot gnu.org [this message]
2011-02-21 14:22 ` danglin at gcc dot gnu.org
2011-02-21 16:06 ` jakub at gcc dot gnu.org
2011-02-23  0:47 ` aoliva 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-47106-4-C0MHHzp4nh@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).