public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl 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: Fri, 08 Apr 2005 01:21:00 -0000 [thread overview] Message-ID: <20050408012111.16954.qmail@sourceware.org> (raw) In-Reply-To: <20031117013315.13082.kargl@12-230-81-20.client.attbi.com> ------- Additional Comments From kargl at gcc dot gnu dot org 2005-04-08 01:21 ------- (In reply to comment #25) > > I do not understand your tone. There is a compiler, g77, which works and > implements at least the Fortran 77 standard. I don't see any reason why it > should be replaced in the distribution by a compiler which is not yet mature > enough to implement the same standard. Are you aware of the fact that g77 *is completely* broken with respect to the gcc-4.x branch? There is no one who is going to fix the problem because the effort to fix g77 is estimated to be equilavent to implementing an actually F95 compiler. > The attitude expressed in "piss off the people who owe you nothing" > can be very bad for the future of Linux. I don't use linux. Never have, never will. I use FreeBSD on an AMD64 platform where there are no commercially available F95 compilers. I have zero compiler writing experience, yet you'll find that I've contributed 69 patches to make gfortran work. Those patches came about because I need a compiler, and I decided to contribute something to GCC other than whining and making disparaging remarks. I don't know about my fellow contributors, but I find that I have little motivation to continue to work on gfortran occur when indivudals come here to tell us that gfortran is useless. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13082
next prev parent reply other threads:[~2005-04-08 1:21 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 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 [this message] 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=20050408012111.16954.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: linkBe 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).