This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [Java] Clean-up TREE_OVERFLOW usage in the Java front-end
- From: Andrew Haley <aph at redhat dot com>
- To: Roger Sayle <roger at eyesopen dot com>
- Cc: gcc-patches at gcc dot gnu dot org, <java-patches at gcc dot gnu dot org>
- Date: Wed, 8 Jun 2005 18:26:02 +0100
- Subject: Re: [Java] Clean-up TREE_OVERFLOW usage in the Java front-end
- References: <Pine.LNX.4.44.0506081115590.7078-100000@www.eyesopen.com>
Roger Sayle writes:
>
> This patch is a repost of the java front-end bits of my previous patch
> http://gcc.gnu.org/ml/gcc-patches/2005-04/msg02412.html to clean-up
> the use of TREE_OVERFLOW in the compiler. Currently, TREE_OVERFLOW
> is only ever set for constant class tree codes, such as INTEGER_CST.
> By restricting the testing of TREE_OVERFLOW to the appropriate tree
> nodes, we can introduce stricter checking in the middle-end.
>
>
> The following patch has been tested on i686-pc-linux-gnu with a
> full "make bootstrap", all default languages, and regression tested
> with a top-level "make -k check" with no new failures.
>
> Ok for mainline?
>
>
> 2005-06-08 Roger Sayle <roger@eyesopen.com>
>
> * typeck.c (convert): Only clear TREE_OVERFLOW on INTEGER_CST nodes.
OK.
Andrew.