From: Stephen Pisuk <smp@ll.mit.edu>
To: John Love-Jensen <eljay@adobe.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Float to Int Conversions
Date: Tue, 26 Feb 2002 08:42:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.44.0202261134320.20318-100000@lager> (raw)
In-Reply-To: <3C7BB6ED.11E6155E@adobe.com>
No I had not, but it didn't help
If the result of the conversion is an INT
the conversion saturates at 0x80000000
however if the result is an UNSIGNED INT
the conversion is correct;
> Hi Stephen,
>
> Have you set IEEE 754 compliance on both compilers?
>
> GCC -ffloat-store
>
> I don't know what MSVC uses.
>
> --Eljay
>
>
__________________________________________________
Stephen Pisuk
MIT Lincoln Laboratory, Room C-472
244 Wood St., Lexington, MA 02420-9108
voice: (781)-981-3682 fax: (781)-981-4583
e-mail: smp@ll.mit.edu
next prev parent reply other threads:[~2002-02-26 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 8:14 Stephen Pisuk
2002-02-26 8:38 ` John Love-Jensen
2002-02-26 8:42 ` Stephen Pisuk [this message]
2002-02-26 11:11 ` John Love-Jensen
2002-02-26 9:35 ` building on MacOS 10.1.3? sbloch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.44.0202261134320.20318-100000@lager \
--to=smp@ll.mit.edu \
--cc=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).