This is the mail archive of the gcc-patches@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]
Other format: [Raw text]

Re: Squelch HOST_FLOAT_WORDS_BIG_ENDIAN


>>>>> "Zack" == Zack Weinberg <zack at codesourcery dot com> writes:

Tom> You could try `make header-check' in the target build directory,
Tom> but I haven't run that target in a long time and I really have no
Tom> idea if it works at all.

Zack> I get floods of errors, starting with:

I'm not too surprised.  Just ignore this.

Zack>   static const jdouble NaN =  0x1.8000000000000p+2047;

Zack> It looks like I have my is-it-finite check backward.  Will revise and
Zack> resubmit.

Thanks.  If you could write a little program to check that one or more
of these constants is correct, that would be helpful.  Easiest is
probably to just cut-and-paste the relevant output into a pure C++
program (writing CNI code to do this is more effort).

Tom> Is there no way to get jcf-dump to print a non-hex value?  This
Tom> program is used for inspecting class files.  Having hex output is less
Tom> useful than printing the constant the way one would expect.

Zack> I believe I can do that by using ldexp().  That may mean we have to
Zack> link jcf-dump against libm, though.  (Not necessary on Linux, NetBSD,
Zack> or Solaris, but all these are relatively boring systems with respect
Zack> to weird portability issues.)

If it's possible without a lot of work, this is preferable.  If it
isn't possible, well, I don't remember ever looking at a float or
double constant in jcf-dump's output.

Tom


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