public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45742] VOLATILE has no effect
Date: Fri, 12 Nov 2010 22:13:00 -0000 [thread overview]
Message-ID: <bug-45742-4-j4GBKy7hpU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45742-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45742
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2010-11-12 21:56:08 UTC ---
(In reply to comment #2)
> (In reply to comment #1)
> > Apparently, VOLATILE has no effect at all. Another test case:
> [...]
> > Tobias, any ideas?
>
> No idea:
>
> $ cat test.f90.003t.original
> ...
> integer(kind=4) b;
> volatile integer(kind=4) j;
>
> b = ((j + j) + j) + j;
I see:
foo (integer(kind=4) & restrict j)
{
integer(kind=4) b;
b = ((*j + *j) + *j) + *j;
{
struct __st_parameter_dt dt_parm.0;
so the volatile is missing. Huh?
This may be a Heisenbug. Unfortunately, valgrind doesn't work on
my system.
next prev parent reply other threads:[~2010-11-12 22:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45742-4@http.gcc.gnu.org/bugzilla/>
2010-11-12 20:09 ` tkoenig at gcc dot gnu.org
2010-11-12 20:26 ` burnus at gcc dot gnu.org
2010-11-12 20:55 ` burnus at gcc dot gnu.org
2010-11-12 22:13 ` tkoenig at gcc dot gnu.org [this message]
2010-11-12 23:06 ` burnus at gcc dot gnu.org
2010-11-12 23:34 ` burnus at gcc dot gnu.org
2010-11-12 23:35 ` burnus at gcc dot gnu.org
2010-11-13 0:15 ` burnus at gcc dot gnu.org
2010-11-13 1:15 ` burnus at gcc dot gnu.org
2010-11-13 11:47 ` burnus at gcc dot gnu.org
2010-11-13 12:55 ` burnus at gcc dot gnu.org
2010-11-13 17:31 ` burnus at gcc dot gnu.org
2010-11-13 17:31 ` burnus at gcc dot gnu.org
2010-11-13 17:39 ` 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-45742-4-j4GBKy7hpU@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).