public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Todd Stock <toddastock@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5668: finit$ not called while using a constructor
Date: Tue, 12 Feb 2002 11:16:00 -0000	[thread overview]
Message-ID: <20020212191602.8705.qmail@sources.redhat.com> (raw)

The following reply was made to PR java/5668; it has been noted by GNATS.

From: Todd Stock <toddastock@yahoo.com>
To: toddastock@yahoo.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/5668: finit$ not called while using a constructor
Date: Tue, 12 Feb 2002 11:12:13 -0800

 Unidiff for bug 5668:
 
 Index: gcc/java/parse.y
 ===================================================================
 RCS file: /cvsroot/gcc/gcc/gcc/java/parse.y,v
 retrieving revision 1.350
 diff -u -r1.350 parse.y
 --- gcc/java/parse.y	4 Feb 2002 02:38:16 -0000	1.350
 +++ gcc/java/parse.y	12 Feb 2002 19:09:48 -0000
 @@ -10690,9 +10690,11 @@
        func = build1 (NOP_EXPR, build_pointer_type (TREE_TYPE (method)), func);
      }
  
 -  if (TREE_CODE (patch) == CALL_EXPR)
 +  if (TREE_CODE (patch) == CALL_EXPR) {
 +    int save_can_complete_normal = CAN_COMPLETE_NORMALLY(patch);
      patch = build_call_or_builtin (method, func, args);
 -  else
 +    CAN_COMPLETE_NORMALLY(patch) = save_can_complete_normal;
 +  } else
      {
        TREE_TYPE (patch) = TREE_TYPE (TREE_TYPE (method));
        TREE_OPERAND (patch, 0) = func;
 @@ -12460,6 +12462,7 @@
      {
        tree super_wfl = build_wfl_node (super_identifier_node);
        tree a = NULL_TREE, t;
 +      CAN_COMPLETE_NORMALLY(super_wfl)=1;
        /* If we're dealing with an anonymous class, pass the arguments
           of the crafted constructor along. */
        if (ANONYMOUS_CLASS_P (DECL_CONTEXT (mdecl)))
 @@ -12468,7 +12471,9 @@
  	  for (; t != end_params_node; t = TREE_CHAIN (t))
  	    a = tree_cons (NULL_TREE, build_wfl_node (TREE_PURPOSE (t)), a);
  	}
 -      return build_method_invocation (super_wfl, a);
 +      a=build_method_invocation (super_wfl, a);
 +      CAN_COMPLETE_NORMALLY(a)=1;
 +      return a;
      }
  }
 
 gcc-gnats@gcc.gnu.org wrote:
 
 >Thank you very much for your problem report.
 >It has the internal identification `java/5668'.
 >The individual assigned to look at your
 >report is: unassigned. 
 >
 >>Category:       java
 >>Responsible:    unassigned
 >>Synopsis:       finit$ not called while using a constructor
 >>Arrival-Date:   Tue Feb 12 09:36:00 PST 2002
 >>
 >
 
 
 
 
 _________________________________________________________
 Do You Yahoo!?
 Get your free @yahoo.com address at http://mail.yahoo.com
 


             reply	other threads:[~2002-02-12 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 11:16 Todd Stock [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-15  2:46 bryce
2002-02-20 12:46 apbianco
2002-02-12 10:46 Todd Stock
2002-02-12 10:26 Alexandre Petit-Bianco
2002-02-12  9:36 toddastock

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=20020212191602.8705.qmail@sources.redhat.com \
    --to=toddastock@yahoo.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).