public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50619] Surprising interaction between -finit-real=NAN and the associate construct
Date: Wed, 05 Oct 2011 08:25:00 -0000 [thread overview]
Message-ID: <bug-50619-4-0tZvI39qf6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50619-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50619
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
CC| |burnus at gcc dot gnu.org,
| |janus at gcc dot gnu.org
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-10-05 08:25:21 UTC ---
This seems to be an ordering problem - from -fdump-tree-original:
test (struct test_ty & restrict e)
{
{
real(kind=4) * rmult;
{
I/O before ASSOCIATE ...
}
rmult = &e->rmult;
*rmult = Nan;
{
I/O in ASSOCIATE ...
}
The "*rmult = NaN" line should be before "rmult = &e->rmult". I don't quite see
whether that's a problem of inserting the NAN or of the ASSOCIATE assignment.
next prev parent reply other threads:[~2011-10-05 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 22:00 [Bug fortran/50619] New: " fkrogh#gcc at mathalacarte dot com
2011-10-05 8:25 ` burnus at gcc dot gnu.org [this message]
2011-11-30 21:35 ` [Bug fortran/50619] " bdavis at gcc dot gnu.org
2012-06-04 9:44 ` gcc.10.dimsea at spamgourmet dot org
2012-06-04 12:32 ` burnus at gcc dot gnu.org
2012-06-04 21:01 ` burnus at gcc dot gnu.org
2012-06-05 11:57 ` gcc.10.dimsea at spamgourmet dot org
2012-06-05 13:05 ` burnus at gcc dot gnu.org
2012-06-14 13:05 ` burnus at gcc dot gnu.org
2012-06-14 13:07 ` burnus at gcc dot gnu.org
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-50619-4-0tZvI39qf6@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: 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).