public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thomas.orgis at awi dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53778] bad code (delivering NaN instead of proper result) with -foptimize-sibling-calls Date: Wed, 27 Jun 2012 08:59:00 -0000 [thread overview] Message-ID: <bug-53778-4-xtcSyPKPrE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53778-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53778 --- Comment #2 from Thomas Orgis <thomas.orgis at awi dot de> 2012-06-27 08:58:57 UTC --- Created attachment 27710 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27710 tarball with complete source to reproduce the issue Ok, then, I feared as much. After taking too much time off the work I get actually paid for (did I say that scientific programming sucks?) ... here is a tarball that reproduces the issue for me and is hopefully small enough to serve as a starting point. It is a set of modules, most of which should not be relevant, just tedious to eliminate. The important sources are datafield.f90, bottomwind.f90 and perturb.f90 ... well just start from dat_init_wind(), which exhibits the bug when called just after dat_init_density() (with inside call to pert_perturb()).
next prev parent reply other threads:[~2012-06-27 8:59 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-26 9:37 [Bug fortran/53778] New: " thomas.orgis at awi dot de 2012-06-26 12:29 ` [Bug fortran/53778] " burnus at gcc dot gnu.org 2012-06-27 8:59 ` thomas.orgis at awi dot de [this message] 2012-06-27 9:03 ` thomas.orgis at awi dot de 2012-06-27 13:44 ` dominiq at lps dot ens.fr 2012-06-27 15:27 ` burnus at gcc dot gnu.org 2012-06-27 21:31 ` thomas.orgis at awi dot de 2012-06-27 21:34 ` thomas.orgis at awi dot 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=bug-53778-4-xtcSyPKPrE@http.gcc.gnu.org/bugzilla/ \ --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).