This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH COMMITTED: Don't break tests for enum in range
- From: Tom Tromey <tromey at redhat dot com>
- To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Cc: iant at google dot com, ebotcazou at adacore dot com, gcc at gcc dot gnu dot org
- Date: Fri, 08 Jun 2007 11:53:18 -0600
- Subject: Re: PATCH COMMITTED: Don't break tests for enum in range
- References: <m38xax41qf.fsf@localhost.localdomain> <200706062015.10039.ebotcazou@adacore.com> <m3tztkztmt.fsf@localhost.localdomain> <200706071215.25222.ebotcazou@adacore.com> <m3fy53yi0b.fsf@localhost.localdomain> <10706071504.AA05478@vlsi1.ultra.nyu.edu>
- Reply-to: tromey at redhat dot com
>>>>> "Richard" == Richard Kenner <kenner@vlsi1.ultra.nyu.edu> writes:
Richard> The simplest example of that is an uninitialized variable.
Richard> I think the best approach is to use flags set by the front
Richard> end to indicate which of these is to be the case. For C, I
Richard> believe (1) is always the proper meaning. I don't know what
Richard> it is for C++, Fortran, and Java.
With Java the middle end should never see an uninitialized variable.
Uninitialized variables are precluded by the language definition, or
the bytecode verifier.
Tom