This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
A possible bug in parsing floating point numbers.
- From: Kazu Hirata <kazu at hxi dot com>
- To: zack at codesourcery dot com
- Cc: gcc-bugs at gcc dot gnu dot org
- Cc: tm at mail dot kloo dot net
- Subject: A possible bug in parsing floating point numbers.
Hi Zack,
March 23, 2002
http://gcc.gnu.org/ml/gcc-cvs/2002-03/msg00999.html
March 25, 2002
http://gcc.gnu.org/ml/gcc-cvs/2002-03/msg01122.html
The first patch breaks the build of the h8300 port during compilation
of libgcc2.c. With the second patch, the h8300 port builds again, but
I get ".long 0" in an assembly output for any floating point constant.
Since you seem to have done some cleanup/fix on the lexical analysis
of floating point numbers, I am wondering if you could give me some
insight into this problem. Here is what's happening.
float foo () { return 1.0; } /* The constant is 1.0. */
.section .rodata
.align 2
.LC0:
.long 0 <- But the constant is not 1.0...
.section .text
.align 1
.global _foo
_foo:
mov.l @.LC0,er0
rts
By the way, I use --target=h8300-hms to configure binutils and gcc.
Thanks,
Kazu Hirata