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/19292] New: [metabug] g77 features lacking in gfortran
Date: Thu, 06 Jan 2005 14:39:00 -0000 [thread overview]
Message-ID: <20050106143936.19292.tobi@gcc.gnu.org> (raw)
This is a metabug for all issues in gfortran that need to be resolved before
gfortran can be used as a complete replacement for g77.
I'm not sure about the following bugs:
- PR 15553 : does this also occur without explicit interfaces? IOW is it
possible to provoke this error in Fortran 77 code?
- PR 18833 : I'm not sure if this is valid Fortran 77
--
Summary: [metabug] g77 features lacking in gfortran
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: tobi at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
BugsThisDependsOn: 5900,12884,13082,13257,13939,14067,14994,15234,15235,152
66,15326,15332,15382,15966,16435,16436,16465,16511,16531
,16580,16907,17229,17285,17423,17472,17675,17737,17871,1
7941,17992,18026,18210,18398,18481,18518,18540,18576,186
00,18714,18737,18781,18794,18827,18870,18879,18977,18982
,19021,19052,19155,19216,19280
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19292
next reply other threads:[~2005-01-06 14:39 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 14:39 tobi at gcc dot gnu dot org [this message]
2005-01-06 14:50 ` [Bug fortran/19292] " pinskia at gcc dot gnu dot org
2005-01-06 14:50 ` pinskia at gcc dot gnu dot org
2005-01-06 17:28 ` Thomas dot Koenig at online dot de
2005-01-06 17:35 ` tobi at gcc dot gnu dot org
2005-01-07 14:02 ` pinskia at gcc dot gnu dot org
2005-01-08 5:40 ` sgk at troutmask dot apl dot washington dot edu
2005-01-09 22:59 ` pbrook at gcc dot gnu dot org
2005-01-09 23:16 ` ebotcazou at gcc dot gnu dot org
2005-01-12 22:17 ` toon at moene dot indiv dot nluug dot nl
2005-01-16 23:21 ` pbrook at gcc dot gnu dot org
2005-01-17 11:05 ` Thomas dot Koenig at online dot de
2005-01-20 10:47 ` [Bug fortran/19292] [meta-bug] " Thomas dot Koenig at online dot de
2005-01-22 22:33 ` pbrook at gcc dot gnu dot org
2005-01-23 0:25 ` dje at gcc dot gnu dot org
2005-01-23 22:38 ` pbrook at gcc dot gnu dot org
2005-01-29 15:39 ` pinskia at gcc dot gnu dot org
2005-02-19 12:59 ` wilson at gcc dot gnu dot org
2005-02-20 22:21 ` kargl at gcc dot gnu dot org
2005-02-22 13:07 ` pinskia at gcc dot gnu dot org
2005-02-24 14:32 ` rth at gcc dot gnu dot org
2005-03-11 14:17 ` pinskia at gcc dot gnu dot org
2005-03-13 19:10 ` tobi at gcc dot gnu dot org
2005-03-13 19:29 ` tobi at gcc dot gnu dot org
2005-03-14 20:17 ` tobi at gcc dot gnu dot org
2005-03-16 0:19 ` fengwang at gcc dot gnu dot org
2005-03-16 14:32 ` tobi at gcc dot gnu dot org
2005-03-17 2:14 ` pinskia at gcc dot gnu dot org
2005-03-22 22:17 ` fxcoudert at gcc dot gnu dot org
2005-03-22 23:19 ` tobi at gcc dot gnu dot org
2005-03-25 7:07 ` fxcoudert at gcc dot gnu dot org
2005-03-25 13:37 ` fxcoudert at gcc dot gnu dot org
2005-03-26 17:44 ` pinskia at gcc dot gnu dot org
2005-04-03 8:10 ` fxcoudert at gcc dot gnu dot org
2005-04-06 9:54 ` fxcoudert at gcc dot gnu dot org
2005-04-08 11:12 ` fxcoudert at gcc dot gnu dot org
2005-04-20 1:10 ` milan at cmm dot ki dot si
2005-04-20 1:15 ` pinskia at gcc dot gnu dot org
2005-04-23 16:11 ` pault at gcc dot gnu dot org
2005-04-23 16:14 ` pault at gcc dot gnu dot org
2005-04-23 16:15 ` pault at gcc dot gnu dot org
2005-04-23 16:18 ` pault at gcc dot gnu dot org
2005-04-24 14:01 ` tobi at gcc dot gnu dot org
2005-04-30 17:53 ` pinskia at gcc dot gnu dot org
2005-05-03 7:05 ` tkoenig at gcc dot gnu dot org
2005-05-03 19:47 ` tkoenig at gcc dot gnu dot org
2005-05-03 19:50 ` tkoenig at gcc dot gnu dot org
2005-05-03 19:52 ` tkoenig at gcc dot gnu dot org
2005-05-05 23:26 ` pinskia at gcc dot gnu dot org
2005-05-11 11:18 ` pinskia at gcc dot gnu dot org
2005-05-15 3:25 ` pinskia at gcc dot gnu dot org
2005-05-31 17:01 ` ebotcazou at gcc dot gnu dot org
2005-06-16 22:29 ` fxcoudert at gcc dot gnu dot org
2005-06-16 23:04 ` fxcoudert at gcc dot gnu dot org
2005-06-17 16:25 ` fxcoudert at gcc dot gnu dot org
2005-07-01 22:11 ` pinskia at gcc dot gnu dot org
2005-07-07 9:56 ` fengwang at gcc dot gnu dot org
2005-07-09 12:14 ` tobi at gcc dot gnu dot org
2005-07-12 4:25 ` pinskia at gcc dot gnu dot org
2005-07-12 4:26 ` pinskia at gcc dot gnu dot org
2005-07-12 4:26 ` pinskia at gcc dot gnu dot org
2005-07-14 15:23 ` pault at gcc dot gnu dot org
2005-07-16 20:54 ` pinskia at gcc dot gnu dot org
2005-07-19 8:48 ` fxcoudert at gcc dot gnu dot org
2005-07-19 21:45 ` steven at gcc dot gnu dot org
2005-08-02 10:52 ` fxcoudert at gcc dot gnu dot org
2005-08-06 13:35 ` pinskia at gcc dot gnu dot org
2005-08-31 12:52 ` fxcoudert at gcc dot gnu dot org
2005-09-08 18:51 ` rsandifo at gcc dot gnu dot org
2005-09-09 22:17 ` pinskia at gcc dot gnu dot org
2005-09-09 22:17 ` pinskia at gcc dot gnu dot org
2005-09-12 11:07 ` tobi at gcc dot gnu dot org
2005-09-16 8:57 ` fxcoudert at gcc dot gnu dot org
2005-09-18 19:53 ` tkoenig at gcc dot gnu dot org
2005-09-29 21:33 ` 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=20050106143936.19292.tobi@gcc.gnu.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).