[llvm-commits] CVS: llvm/docs/LangRef.html

[Chris Lattner]

Thanks for the cleanups Jeff, but...

On Apr 21, 2007, at 6:17 PM, Jeff Cohen wrote:

> @@ -1400,12 +1396,12 @@
>    <dt><b><tt>uitofp ( CST to TYPE )</tt></b></dt>
>    <dd>Convert an unsigned integer constant to the corresponding  
> floating point
>    constant. TYPE must be floating point. CST must be of integer  
> type. If the
> -  value won't fit in the floating point type, the results are  
> undefined.</dd>
> +  value won't fit in the floating point type, precision may be  
> lost.</dd>
>
>    <dt><b><tt>sitofp ( CST to TYPE )</tt></b></dt>
>    <dd>Convert a signed integer constant to the corresponding  
> floating point
>    constant. TYPE must be floating point. CST must be of integer  
> type. If the
> -  value won't fit in the floating point type, the results are  
> undefined.</dd>
> +  value won't fit in the floating point type, precision may be  
> lost.</dd>

..

> @@ -3073,7 +3069,7 @@
>  <h5>Semantics:</h5>
>  <p>The '<tt>uitofp</tt>' instruction interprets its operand as an  
> unsigned
>  integer quantity and converts it to the corresponding floating  
> point value. If
> -the value cannot fit in the floating point value, the results are  
> undefined.</p>
> +the value cannot fit in the floating point value, precision may be  
> lost.</p>
>
>
>  <h5>Example:</h5>
> @@ -3106,7 +3102,7 @@
>  <h5>Semantics:</h5>
>  <p>The '<tt>sitofp</tt>' instruction interprets its operand as a  
> signed
>  integer quantity and converts it to the corresponding floating  
> point value. If
> -the value cannot fit in the floating point value, the results are  
> undefined.</p>
> +the value cannot fit in the floating point value, precision may be  
> lost.</p>

No really, the results *are* undefined.  Please revert these  
changes.  FWIW, these are the same semantics as C.

Thanks Jeff,

-Chris