public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segalemb at usp dot br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/23884] failure in gcc
Date: Fri, 07 Oct 2005 13:57:00 -0000 [thread overview]
Message-ID: <20051007135705.5554.qmail@sourceware.org> (raw)
In-Reply-To: <bug-23884-11330@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from segalemb at usp dot br 2005-10-07 13:57 -------
(In reply to comment #8)
I tried this simple test case:
module param
double precision mutdefc(8,5,7)
data mutdefc(1,1,1) /0.0000d0/
* mutdefc(1,1,2) /0.0000d0/
end module param
and the compilation go straight. Only when all indexes of mutdefc
where equal, the error appears. This indicates that this is not
a duplicate of bug 17737.
> (In reply to comment #7)
> > Note I reduced it using delta so the all of my reduced tescase came exactly
> from the file and nothing
> > else.
>
> This is not true. Even if the constants appearing in the data statements in the
> original code are replaced by their values, there will be no line that reads
> data mutdefc(...,7) /.../
> as all initializations are of the form
> data mutdefc(...,1) /.../
> * mutdefc(...,2) /.../
> ...
> So you did more to the testcase.
>
> Given the error location, I'm inclined to believe that it is indeed a duplicate,
> but your reduced testcase doesn't prove it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23884
next parent reply other threads:[~2005-10-07 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-23884-11330@http.gcc.gnu.org/bugzilla/>
2005-10-07 13:57 ` segalemb at usp dot br [this message]
2005-09-14 18:49 [Bug preprocessor/23884] New: " segalemb at usp dot br
2005-09-14 18:55 ` [Bug fortran/23884] " pinskia at gcc dot gnu dot org
2005-09-14 19:30 ` pinskia at gcc dot gnu dot org
2005-09-23 19:12 ` segalemb at usp dot br
2005-09-23 19:27 ` segalemb at usp dot br
2005-09-29 21:51 ` tobi at gcc dot gnu dot org
2005-09-29 21:54 ` pinskia at gcc dot gnu dot org
2005-09-29 22:10 ` tobi at gcc dot gnu dot 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=20051007135705.5554.qmail@sourceware.org \
--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).