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, 23 Sep 2005 19:27:00 -0000 [thread overview]
Message-ID: <20050923192729.21968.qmail@sourceware.org> (raw)
In-Reply-To: <20050914184726.23884.segalemb@usp.br>
------- Additional Comments From segalemb at usp dot br 2005-09-23 19:27 -------
Subject: Re: failure in gcc
I and another person searched carrefully the source code and there
is no repeated data commands.
Sergio
Citando pinskia at gcc dot gnu dot org <gcc-bugzilla@gcc.gnu.org>:
>
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-14
> 19:29 -------
> Reduced testcase:
> module param
> double precision mutdefc(8,5,7)
> data mutdefc(1,1,7) /0.0000d0/
> * mutdefc(1,1,7) /0.0000d0/
> end module param
>
> But this is really a dup of bug 17737
>
> *** This bug has been marked as a duplicate of 17737 ***
>
> --
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|WAITING |RESOLVED
> Resolution| |DUPLICATE
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23884
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23884
next prev parent reply other threads:[~2005-09-23 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[not found] <bug-23884-11330@http.gcc.gnu.org/bugzilla/>
2005-10-07 13:57 ` segalemb at usp dot br
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=20050923192729.21968.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).