public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jeroen dobbelaere <jeroen.dobbelaere@acunia.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/5828: gcc-3.0.4 on arm : floating point registers incorrectly reloaded Date: Tue, 05 Mar 2002 02:56:00 -0000 [thread overview] Message-ID: <20020305105602.14527.qmail@sources.redhat.com> (raw) The following reply was made to PR target/5828; it has been noted by GNATS. From: jeroen dobbelaere <jeroen.dobbelaere@acunia.com> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, jeroen.dobbelaere@acunia.com, gcc-bugs@gcc.gnu.org Cc: Subject: Re: target/5828: gcc-3.0.4 on arm : floating point registers incorrectly reloaded Date: Tue, 05 Mar 2002 11:43:37 +0100 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5828 Following testprogram can be used to verify Try with : g++ -Wall -O float-reload-jdo-1.cpp ./a.out g++ -Wall -O2 float-reload-jdo-1.cpp ./a.out g++ -Wall -O3 float-reload-jdo-1.cpp ./a.out ********* float-reload-jdo-1.cpp - begin *********** // float-reload-jdo-1.cpp #include <stdio.h> extern void* do_something(int s) throw(int); extern void* do_something_else(int s) throw(int); extern double getADouble(int i); int main(int argc, char* argv[]) { double d0,d1,d2,d3,d4,d5,d6,d7; int i=0; d0=getADouble(i++); d1=getADouble(i++); d2=getADouble(i++); d3=getADouble(i++); d4=getADouble(i++); d5=getADouble(i++); d6=getADouble(i++); d7=getADouble(i++); do_something(1); if(d0 != getADouble(0)) return -1; if(d1 != getADouble(1)) return -1; if(d2 != getADouble(2)) return -1; if(d3 != getADouble(3)) return -1; if(d4 != getADouble(4)) return -1; if(d5 != getADouble(5)) return -1; if(d6 != getADouble(6)) return -1; if(d7 != getADouble(7)) return -1; printf("ok\n"); return 0; } double getADouble(int i) { const double list[8] = { 123.333, 126.784353, 203.03415, 220.6234605, 0.000134315123, 9384.239451, 1239487157834, 9328432.234 }; return list[i]; } void* do_something(int s) throw(int) { return do_something_else(s); } void* do_something_else(int s) throw(int) { switch(s) { case 0: return 0; case 1: return (void*)1; default: throw s; } } ********* float-reload-jdo-1.cpp - end ***********
next reply other threads:[~2002-03-05 10:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-05 2:56 jeroen dobbelaere [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-14 7:54 rearnsha 2002-03-14 7:16 Richard Earnshaw 2002-03-06 3:46 jeroen dobbelaere 2002-03-06 2:36 Richard Earnshaw 2002-03-05 2:56 jeroen dobbelaere 2002-03-04 7:06 jeroen.dobbelaere
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=20020305105602.14527.qmail@sources.redhat.com \ --to=jeroen.dobbelaere@acunia.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).