public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mark@klomp.org
To: gcc-gnats@gcc.gnu.org
Subject: java/5942: tree check failure when compiling Classpath with strictfp StrictMath class
Date: Wed, 13 Mar 2002 11:36:00 -0000	[thread overview]
Message-ID: <20020313193543.13315.qmail@sources.redhat.com> (raw)


>Number:         5942
>Category:       java
>Synopsis:       tree check failure when compiling Classpath with strictfp StrictMath class
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 13 11:36:04 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     mark@klomp.org
>Release:        gcc version 3.1 20020313 (prerelease)
>Organization:
>Environment:
Debian GNU/Linux (sid/unstable)
>Description:
Compiling a recent Classpath from CVS gives:

/usr/local/gcc-3.1/bin/gcj -C -d . @classes
./../java/security/Identity.java:207: tree check: expected class 't', have 'e' (expr_with_file_location) in unresolved_type_p, at java/parse.y:5028

This problem goes away when you remove the strictfp class modifier from java/lang/StrictMath.java.

(Note that you will soon hit bug #4715 - Tree check failure in check_inner_circular_reference, without the patch in that bug report.)
>How-To-Repeat:
Get either the latest CVS version of GNU Classpath or the latest release (0.0.3). (The latest release does not contain StrictMath yet but adding the strictfp class modifier to java/lang/Math.java gives the same results.)

./configure --with-gjc
make
>Fix:
The following horrible kludge seems to work around it.

--- parse.y     2002/03/12 18:07:32     1.353.2.5
+++ parse.y     2002/03/13 01:30:53
@@ -5025,10 +5025,18 @@
       if (returned)
        {
          tree decl = IDENTIFIER_CLASS_VALUE (EXPR_WFL_NODE (wfl));
-         if (decl && current_class && (decl == TYPE_NAME (current_class)))
+         tree cc = current_class;
+         if (cc && TREE_CODE (cc) == EXPR_WITH_FILE_LOCATION)
+           cc = EXPR_WFL_NODE (cc);
+         if (decl && cc && (decl == TYPE_NAME (current_class)))
            *returned = TREE_TYPE (decl);
          else if (GET_CPC_UN () == EXPR_WFL_NODE (wfl))
-           *returned = TREE_TYPE (GET_CPC ());
+         {
+           if (TREE_CODE (GET_CPC ()) != EXPR_WITH_FILE_LOCATION)
+             *returned = TREE_TYPE (GET_CPC ());
+           else
+             *returned = NULL_TREE;
+         }
          else
            *returned = NULL_TREE;
        }
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-03-13 19:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 11:36 mark [this message]
2002-03-26 10:49 tromey

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=20020313193543.13315.qmail@sources.redhat.com \
    --to=mark@klomp.org \
    --cc=gcc-gnats@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).