https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27394
Andrew Pinski changed:
What|Removed |Added
CC||xiaoyi_wu at yahoo dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27394
Bug 27394 depends on bug 28144, which changed state.
Bug 28144 Summary: floating point constant -> byte/char/short conversion is
wrong for java
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28144
What|Removed |A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27394
Bug 27394 depends on bug 28144, which changed state.
Bug 28144 Summary: floating point constant -> byte/char/short conversion is
wrong for java
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28144
What|Removed |A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27394
Bug 27394 depends on bug 28144, which changed state.
Bug 28144 Summary: floating point constant -> byte/char/short conversion is
wrong for java
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28144
What|Removed |A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27394
Oleg Endo changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
--- Comment #8 from amylaar at gcc dot gnu dot org 2006-11-15 16:28 ---
This is still a quality of implementation issue. Changing the behaviour of the
program when the optimization level changes makes debugging harder, and we
could easily avoid the change in this instance.
--
amylaa
--- Comment #7 from pinskia at gcc dot gnu dot org 2006-05-29 22:19 ---
This is invalid, the conversion is undefined.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #6 from schwab at suse dot de 2006-05-03 09:17 ---
> While the C standard says that the result of the conversion is unspecified,
The standard says that the behaviour is undefined (6.3.1.4#1). That is even
true when converting to unsigned.
--
http://gcc.gnu.org/bugzilla
--- Comment #5 from amylaar at gcc dot gnu dot org 2006-05-02 18:21 ---
(In reply to comment #4)
> (In reply to comment #1)
> > In 3.x, double -> char/int conversion was done consistently with the
> > documented
> > behaviour of integer -> signed integer type conversion.
> > http://gcc.
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-05-02 18:00 ---
(In reply to comment #1)
> In 3.x, double -> char/int conversion was done consistently with the
> documented
> behaviour of integer -> signed integer type conversion.
> http://gcc.gnu.org/onlinedocs/gcc-4.1.0/gcc/In
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-05-02 17:58 ---
See PR 9325 and PR 6391.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27394
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-05-02 17:54 ---
(In reply to comment #1)
> In 3.x, double -> char/int conversion was done consistently with the
> documented
And there is a dup of this bug some where which has been closed and I cannot
find it right now.
--
h
--- Comment #1 from amylaar at gcc dot gnu dot org 2006-05-02 17:53 ---
In 3.x, double -> char/int conversion was done consistently with the documented
behaviour of integer -> signed integer type conversion.
http://gcc.gnu.org/onlinedocs/gcc-4.1.0/gcc/Integers-implementation.html#Integer
13 matches
Mail list logo