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/31298] F2003: use mod, operator(+) => operator(.userOp.) not supported
Date: Sat, 22 Jun 2013 17:26:00 -0000 [thread overview]
Message-ID: <bug-31298-4-nse6MmVl79@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-31298-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31298
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #17 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #16)
> Should not this PR be closed as FIXED (no activity for the past five years)?
Of course not. It's still not implemented. By that argument, we could also
close bugs about UTIO or submodules as FIXED because they haven't be
implemented either.
next prev parent reply other threads:[~2013-06-22 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-31298-4@http.gcc.gnu.org/bugzilla/>
2013-06-22 16:59 ` dominiq at lps dot ens.fr
2013-06-22 17:26 ` burnus at gcc dot gnu.org [this message]
2007-03-21 15:15 [Bug fortran/31298] New: Uninitialized variable in f951 (in read_module) burnus at gcc dot gnu dot org
2007-08-17 8:14 ` [Bug fortran/31298] F2003: use mod, operator(+) => operator(.userOp.) not supported burnus at gcc dot gnu dot org
2007-08-17 15:10 ` patchapp at dberlin dot org
2007-08-26 18:37 ` burnus at gcc dot gnu dot org
2007-08-26 18:43 ` burnus at gcc dot gnu dot org
2008-01-15 15:33 ` burnus at gcc dot gnu dot org
2008-03-14 16:46 ` rguenth at gcc dot gnu dot org
2009-11-01 18:06 ` burnus 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=bug-31298-4-nse6MmVl79@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).