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: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: tromey at redhat dot com
- Cc: ebotcazou at adacore dot com, gcc at gcc dot gnu dot org, iant at google dot com
- Date: Fri, 08 Jun 2007 14:50:33 EDT
- 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> <m34pliwcxd.fsf@fleche.redhat.com>
> With Java the middle end should never see an uninitialized variable.
> Uninitialized variables are precluded by the language definition, or
> the bytecode verifier.
Then if there's no other way in the language to create an undefined value,
Java should certainly use the "undefined" choice, like C.