public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tobi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/13082] Function entries and entries with alternate returns not implemented
Date: Sun, 05 Dec 2004 21:27:00 -0000 [thread overview]
Message-ID: <20041205212702.25677.qmail@sourceware.org> (raw)
In-Reply-To: <20031117013315.13082.kargl@12-230-81-20.client.attbi.com>
------- Additional Comments From tobi at gcc dot gnu dot org 2004-12-05 21:27 -------
*** Bug 18824 has been marked as a duplicate of this bug. ***
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |Thomas dot Koenig at online
| |dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13082
next prev parent reply other threads:[~2004-12-05 21:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 1:33 [Bug fortran/13082] New: ICE with ENTRY statement gcc-bugzilla at gcc dot gnu dot org
2003-11-17 3:11 ` [Bug fortran/13082] [gfortran] " pinskia at gcc dot gnu dot org
2003-11-17 16:14 ` pinskia at gcc dot gnu dot org
2003-11-17 16:28 ` reichelt at gcc dot gnu dot org
2003-12-05 12:19 ` steven at gcc dot gnu dot org
2004-01-05 17:34 ` pinskia at gcc dot gnu dot org
2004-04-26 4:11 ` pinskia at gcc dot gnu dot org
2004-04-26 11:30 ` giovannibajo at libero dot it
2004-05-04 14:48 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-05-13 23:56 ` [Bug fortran/13082] [gfortran] ENTRY statement not implemented tobi at gcc dot gnu dot org
2004-05-26 11:59 ` pinskia at gcc dot gnu dot org
2004-07-12 4:22 ` [Bug fortran/13082] " pinskia at gcc dot gnu dot org
2004-07-13 13:55 ` tobi at gcc dot gnu dot org
2004-08-09 15:51 ` pinskia at gcc dot gnu dot org
2004-08-12 22:07 ` pbrook at gcc dot gnu dot org
2004-08-17 15:34 ` cvs-commit at gcc dot gnu dot org
2004-08-18 10:53 ` reichelt at gcc dot gnu dot org
2004-08-18 11:03 ` paulthomas2 at wanadoo dot fr
2004-08-18 11:05 ` pbrook at gcc dot gnu dot org
2004-08-18 16:47 ` paulthomas2 at wanadoo dot fr
2004-08-29 15:17 ` [Bug fortran/13082] Function entries " tobi at gcc dot gnu dot org
2004-12-05 21:25 ` tobi at gcc dot gnu dot org
2004-12-05 21:26 ` [Bug fortran/13082] Function entries and entries with alternate returns " tobi at gcc dot gnu dot org
2004-12-05 21:27 ` tobi at gcc dot gnu dot org [this message]
2005-01-06 14:40 ` tobi at gcc dot gnu dot org
2005-02-19 15:19 ` pinskia at gcc dot gnu dot org
2005-03-21 21:42 ` federico dot carminati at cern dot ch
2005-03-29 12:35 ` alfredo dot ferrari at cern dot ch
2005-04-07 20:14 ` twilson at ems dot jsc dot nasa dot gov
2005-04-07 22:07 ` kargl at gcc dot gnu dot org
2005-04-07 23:16 ` fasso at slac dot stanford dot edu
2005-04-07 23:28 ` pinskia at gcc dot gnu dot org
2005-04-08 1:21 ` kargl at gcc dot gnu dot org
2005-04-08 7:14 ` fca at mail dot cern dot ch
2005-04-08 7:36 ` Thomas dot Koenig at online dot de
2005-04-08 17:10 ` jakub at gcc dot gnu dot org
2005-04-29 15:33 ` cvs-commit at gcc dot gnu dot org
2005-04-29 16:07 ` cvs-commit at gcc dot gnu dot org
2005-04-30 17:53 ` pinskia at gcc dot gnu dot org
2005-05-15 3:25 ` pinskia 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=20041205212702.25677.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).