public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: gcc-patches@gcc.gnu.org
Subject: Cgraph alias reorg 17/14 (fix ipa-prop computation of varying args)
Date: Sat, 11 Jun 2011 14:50:00 -0000	[thread overview]
Message-ID: <20110611142209.GB3871@kam.mff.cuni.cz> (raw)

Hi,
while breaking up the patch Imissed two pots in ipa-prop, where we need to walk aliases.
This leads to segfault while compiling Mozilla.  Also because alled_with_var_arguments
is recomputed at IPA time, we don't need to stream it.

Bootstrapped/regtested x86_64-linux, comitted.

Honza

Index: ChangeLog
===================================================================
--- ChangeLog	(revision 174954)
+++ ChangeLog	(working copy)
@@ -1,5 +1,12 @@
 2011-06-11  Jan Hubicka  <jh@suse.cz>
 
+	* ipa-prop.c (ipa_make_edge_direct_to_target): Fix code setting varying args.
+	(ipa_update_after_lto_read): Likewise.
+	(ipa_write_node_info): Do not sream call_with_var_arguments.
+	(ipa_read_node_info): Likewise.
+
+2011-06-11  Jan Hubicka  <jh@suse.cz>
+
 	* ipa.c (cgraph_comdat_can_be_unshared_p): Fix pasto.
 
 2011-06-11  Jan Hubicka  <jh@suse.cz>
Index: ipa-prop.c
===================================================================
--- ipa-prop.c	(revision 174951)
+++ ipa-prop.c	(working copy)
@@ -1719,6 +1719,7 @@ ipa_make_edge_direct_to_target (struct c
 	  fprintf (dump_file, "\n");
 	}
     }
+  callee = cgraph_function_or_thunk_node (callee, NULL);
 
   if (ipa_get_cs_argument_count (IPA_EDGE_REF (ie))
       != ipa_get_param_count (IPA_NODE_REF (callee)))
@@ -2815,7 +2816,6 @@ ipa_write_node_info (struct output_block
   lto_output_uleb128_stream (ob->main_stream, node_ref);
 
   bp = bitpack_create (ob->main_stream);
-  bp_pack_value (&bp, info->called_with_var_arguments, 1);
   gcc_assert (info->uses_analysis_done
 	      || ipa_get_param_count (info) == 0);
   gcc_assert (!info->node_enqueued);
@@ -2858,7 +2858,6 @@ ipa_read_node_info (struct lto_input_blo
   ipa_initialize_node_params (node);
 
   bp = lto_input_bitpack (ib);
-  info->called_with_var_arguments = bp_unpack_value (&bp, 1);
   if (ipa_get_param_count (info) != 0)
     info->uses_analysis_done = true;
   info->node_enqueued = false;
@@ -3015,9 +3014,12 @@ ipa_update_after_lto_read (void)
     if (node->analyzed)
       for (cs = node->callees; cs; cs = cs->next_callee)
 	{
+	  struct cgraph_node *callee;
+
+	  callee = cgraph_function_or_thunk_node (cs->callee, NULL);
 	  if (ipa_get_cs_argument_count (IPA_EDGE_REF (cs))
-	      != ipa_get_param_count (IPA_NODE_REF (cs->callee)))
-	    ipa_set_called_with_variable_arg (IPA_NODE_REF (cs->callee));
+	      != ipa_get_param_count (IPA_NODE_REF (callee)))
+	    ipa_set_called_with_variable_arg (IPA_NODE_REF (callee));
 	}
 }
 

                 reply	other threads:[~2011-06-11 14:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110611142209.GB3871@kam.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=gcc-patches@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).