public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zack at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/7285] [ia64] unsigned-to-floating conversion not spec conformant Date: Thu, 18 Mar 2004 10:08:00 -0000 [thread overview] Message-ID: <20040318100829.22014.qmail@sources.redhat.com> (raw) In-Reply-To: <20020712045600.7285.jbeulich@novell.com> ------- Additional Comments From zack at codesourcery dot com 2004-03-18 10:08 ------- Subject: Re: [ia64] unsigned-to-floating conversion not spec conformant Thanks for the additional detail, but I am still not seeing exactly what should happen. (For the record, I used the HP compiler as a reference because it's the non-GCC compiler for IA64 that I have convenient access to; I wasn't expecting its output necessarily to be correct.) This code static __float80 floatunsdixf(unsigned long long x) { return x; } void main(void) { __float80 v = floatunsdixf(12); printf("%qf\n", v); return 0; } does _not_ trigger a denormal exception when executed on ia64-hpux. (On this target "long double" is a software-emulated 128-bit type, you have to use __float80 to get IEEE extended.) I determined this by running the program under GDB, stepi-ing through floatunsdixf(), and printing the value of ar40 (= ar.fpsr) at each step. What gives? Did I pick a bad test constant or something? zw -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7285
next prev parent reply other threads:[~2004-03-18 10:08 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20020712045600.7285.jbeulich@novell.com> 2004-01-28 21:41 ` zack at gcc dot gnu dot org 2004-01-28 21:41 ` zack at gcc dot gnu dot org 2004-03-18 0:30 ` zack at gcc dot gnu dot org 2004-03-18 0:36 ` zack at gcc dot gnu dot org 2004-03-18 8:08 ` jbeulich at novell dot com 2004-03-18 10:08 ` zack at codesourcery dot com [this message] 2004-03-18 10:59 ` jbeulich at novell dot com 2004-06-25 23:45 ` pinskia at gcc dot gnu dot org 2004-09-25 16:36 ` pinskia at gcc dot gnu dot org 2004-12-17 14:30 ` jbeulich at novell dot com 2005-07-05 2:14 ` pinskia at gcc dot gnu dot org 2003-05-22 12:09 ehrhardt@mathematik.uni-ulm.de
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=20040318100829.22014.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).