This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: gcc compiler bug


On Thu, 1 Jun 2000, Dale Williamson wrote:

> Are you hinting that "playing with NaNs" is dangerous?  Nothing

Actually it's not just NaNs.  It's floating point in general.

> Just to move 64 bits from one place to another, implementors of C
> compilers are free to choose not to pass these 64 bits through an
> x87 register that will widen them to 80 bits and meddle with them
> before it spits them out.

But you told gcc 

double funcd() { return X.x; }

and it's part of the x86 ABI to return a double from a function in a
floating point register (what a revolutionary concept!)

Thus you need to know something about the underlying hardware if
you want to examine bit patterns.  This is definitely not a gcc bug.

-- 
Linuxcare.  Support for the Revolution.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]